There are some early studies out [1] that indicate remission is possible with OIT. (For laypeople, "desensitization" ~= can tolerate some peanut exposure without a reaction, but still needs to carry an epipen and remain on the maintenance dose for life, while "remission" ~= no longer has a peanut allergy). The numbers were 71% desensitization and 21% remission for OIT vs. 2% both for a placebo. It was heavily dependent on age, with 71% of 1-year-olds, 35% of 2-year-olds, and 19% of 3-year-olds achieving remission.
Data will be scant at this time, because the full treatment takes a long time and needs to be adhered to closely. It's 30 weeks of OIT, followed by 2 years of a maintenance dose, followed by a 6-month hiatus to verify whether the maintenance dose can be stopped while still achieving remission, so data necessarily lags the start of any clinical trials by 3+ years.
> Often a deal-breaker for the more privacy-conscious people, unfortunately
You can’t have conversation in your community without them being public either. Saying anything in discord is just as public as on the middle of a busy shopping street.
> Well, you move the type checks from the database to the app, effectively, which is not a new idea by any means (and a bad idea in many cases), but with JSON, it can actually work out nicely-ish, as long as there are no significant relationships between tables.
That way you're throwing away 50% of the reason you use a relational database in the first place. Has it occurred to you that MongoDB exists?
Also I don't understand why you're afraid of migrations, especially since you're the only developer on your own SMTP server.
File descriptors and file descriptions are not the same thing. Descriptors are references to descriptions, along with some metadata, and multiple descriptors can point to the same descriptor.
I'm sure Viktor Orban thinks he's doing what's best for Hungary, too. It doesn't really matter whether they think they're justified when their values are so alien that you can't reconcile your ideals with theirs. You may as well tell a sick patient that they're being unreasonable because the virus isn't actually a sentient being trying to destroy your body's cells, it's just programmed to reproduce like that.
> decided cheap labor was more important than national security
Organized labor is considered a threat to national security, it's no coincidence that deindustrialization followed a period of widespread labor militancy.
I recall something similar from my first job, except the shared file locking was a full on feature in Macromedia dreamweaver.
CSS was just starting to get adopted and every project we worked on just had one “gobal.css” file. Inevitably, everyday someone would leave the office and forget to unlock global.css and no one else could get anything done.
I have to imagine that a big part of any solution to review gaming and bot spam is data diversity. eg: whether the submitter has been within X meters of the thing they're reviewing in the last Y days.
Google seems to have done a good job with review spam on Google Maps, better than their job with SEO spam and malicious search results, and deep+diverse datasets are effectively Alphabet's (not just Google's) entire business.
Yelp would have a very hard time getting to know as much about review submitters, an open data platform would have a hard time gathering even what Yelp already collects.
I agree. I love coding and don't think I'd like non-creative work as much, but there's definitely nothing wrong with trades; it's honorable work, and I'd encourage anyone to seriously consider it if they weren't sure what they wanted to do.
The conclusion to the article has some pretty good points regarding configuration languages; I wonder if any present language satisfies all or most of those points.
I am an adult who takes beginner lessons from a teacher and he says with new students he often has to undo the “learning” from (sometimes years of) those apps - and it can often be devastating to the ego, especially for kids.
Agreed. And he probably doesn't even have to. (Incidentally, swing by your local big box store at closing time and ask the guys in plumbing if they want to make $500 or $1000 by putting in a water heater tonight; that worked for me, anyway, even on a Friday night.)
I just paid $4,000 for a very experienced plumber and his apprentice to replace a tankless water heater that I could buy new on Ebay for $1,200. That extra $2,800 was pure profit for a job that took four or five hours, and I also had to wait a day before he could fit me in.
i live in a city with a population of 14 million people, but still most of my everyday transactional interactions like buying churros, chicken wings, or electrical supplies are with people i know and transact with repeatedly. that's because i walk there, lacking a motor vehicle. i imagine this was also true of day-to-day commerce in ancient rome, and of course the patron-client and master-slave relationships that were so central in roman society were anything but anonymous
For me the "uv" manager has changed my Python experience because: (1) it has a correct resolver whereas "pip" certainly doesn't and I'm not sure about poetry, (2) it is crazy fast, (3) "uv" is just a binary which I can pip into my system.
(3) is important because if it was written in Javascript or Java or Python or .NET or many other languages I'd have to learn something about the runtimes of those environment to get it working. If it was written in Python it would have to deal with the bootstrapping problem that it ought to have it's own Python installation separate from the one that it is manipulating so it can't have conflicts with that environment. (e.g. how many times have I busted my poetry?) I can use "uv" or "ruff" without learning anything about Rust!
As for (2) the speed of "uv" has as much to do with better algorithms and caching as it does with being in Rust and thus much faster than Python. I think you could have done better than Poetry in Python but "uv" is transformative in that it can often build an environment in seconds or less whereas with "poetry" or "pip" or "conda" I might have time to pound out a few posts on HN. I used to avoid creating new Python environments as much as possible but now it is fast, easy, and even fun.
I bet it is more work to write "uv" in rust as opposed to a similar tool in Python but the impact on the community is so huge because we can finally put problem (1) behind us and do it with speed, reliability and grace. I had notes on how to build a better python package management system and sometimes thought about trying it but I'd become convinced that the social problem of too many people finding half-baked tools like "pip" and "poetry" acceptable was intractable. Thanks to "uv" nobody will ever have to write one.
If you look at the CIE Lab def and the HCT definition that Google uses it makes the math more clear....as with HCT there is a perception adjustment mathematically calculated
Same here. If your entities are modelled mostly correctly you really don't have to worry about migrations that much. It's a bit of a red herring and convenient "problem" pushed by the NoSQL camp.
On a relatively neat and well modelled DB, large migrations are usually when relationships change. E.g. One to many becomes a many to many.
Really the biggest hurdle is managing the change control to ensure it aligns with you application. But that's a big problem with NoSQL DB deployments too.
At this point I don't even want to hear what kind of crazy magic and "weird default and fallback" behavior the schema less NoSQL crowd employs. My pessimistic take is they just expose the DB onto GraphQL and make it front ends problem.
That notation is used sometimes in the literature on model alloys. This does not survive contact with engineering, where they tweak the formula to a hundredth of a percent.
Strictly speaking, this is not at all true. Eyes are pretty bad at this, much worse than cameras have been for a long while.
Vision, however, is much better. This is because of all of the postprocessing our brains do with the raw information our eyes put out before we actually "see" what our eyes are pointing at. But even that is full of errors (think optical illusions).
I think, if the WSJ wants to make me a believer in "skip college and join the workforce," the can promote things like better labor laws, universal health care, and a social safety net. Instead of the opposite, that is.
The physical conditions of blue collar jobs vary widely. The tradesmen who come to work on jobs at my house, if they're my age, look 20 years older. Most are hobbling. Many will stop working before 60, or end up in lower paying jobs such as retail, that are less physical. They have to keep working because they have no retirement.
Many occupations are seasonal, or cyclic. The construction industry is fickle.
Many occupations involve mostly smaller businesses that are "below the radar" of OSHA and other regulations. Many of the smaller businesses are family owned, meaning that your chances depend on connections and favors. The ability to move up into an ownership position may depend on family wealth.
Some skilled trades are nicer, such as many health care jobs, but still involve physical work.
Granted I'm only mentioning the extremes, and not everybody can be a computer programmer.
I'm honestly not sure how big a problem that was. If anything, critics tend towards the the new and unusual because they're bored. The problem is much more that no one is willing to pay for them.
Data will be scant at this time, because the full treatment takes a long time and needs to be adhered to closely. It's 30 weeks of OIT, followed by 2 years of a maintenance dose, followed by a 6-month hiatus to verify whether the maintenance dose can be stopped while still achieving remission, so data necessarily lags the start of any clinical trials by 3+ years.
[1] https://www.nih.gov/news-events/news-releases/oral-immunothe...