skysight-inc/HackerNews huggingface dataset:
> I started talking with the driver about crime surges, mainly the dramatic car jackings increase. He said 22 people he personally knew have been victims of car jacking in 2021.

This sounds like a typical made-up crime panic narrative, honestly. The linked story being about a car left running with an infant in it being stolen doesn't help. Terrible, but not at all some boxed-in high octane car theft.

Sibling posts chimed in about actually living there and this not being a thing. I don't live there, so can only search the news, but any stories about car thefts I'm seeing include warnings from the police for people to stop leaving their cars heating up with the keys in them.

We should endeavor to not buy into moral panics but act on data. We've seen from history that good reactions basically never come from decisive responses to crime waves that are actually constructed narratives from a data point or two.
The training simulators used custom hardware from Marconi Simulation as well - a long long time ago I didn't get to job to work on them at Torness.

Mind you I did end up on an academic project that included modelling of Hunterston, so I got the "behind the scenes" tour there that Charlie got for Torness.

The Project Manager from Scottish Nuclear had worked on the construction of Torness and he lots of interesting stories.
I mean, it seems like Inc's pretty clear in their position that Google could just pay for the technology they infringed ("The company doesn't want to pay Sonos for technology it copied") rather than backtrack on features they promised their users, and it's a point that stands pretty well on its own without even needing a long article to back it, though this certainly helps their readers with the background behind what's going on.

I'm keen on seeing whether Google ends up on the receiving end of a class action suit for disabling features that were sold to customers and then disabled after the fact.
How? I don't use Chrome.
I think I can agree with that. Although defamation is probably a grey area. If I say, “the vice president is corrupt and unintelligent”, should I not be allowed to speak that opinion?
My old man was a Navy nuke turned instrument tech at Three Mile Island... he can go on and on about steam tables.

I worked there one refueling outage while lazing about after college. Highlights include: sweeping river muck out of the empty cooling towers, scrubbing pipes for x-ray analysis, standing "fire watch" since doors were propped open, taking a smoke break on top of the Unit 2 control room building (that Unit 2), staring at the humongous, partially-disassembled turbine (they may have replaced it that year), spotlighting deer at the end of the island. I also remember a very strange feeling while listening to radiation monitors go crazy when the spent fuel was being removed... if you walked a few dozen feet past the warning tape you were probably dead.
Thanks for the input, and yes it all sounds very complicated. The tip about using MSTR as a proxy does sound appealing, particularly as I'm not much of a fan of their product anyway.
Google is the best search engine for searching ads.
Haven't thought of this, I guess for some people it makes sense especially for small, personal projects. I'm more biased towards startups with a plan to grow or larger projects.

In my case if the hosting provider doesn't have something like DigitalOcean's droplets I'll still rely on docker compose instead of the default stack deployed on the system whatever stack I'm choosing. But yeah that's raising the bar too much for most people especially for a couple of scripts or pages.
The methodology in this article is terrible. It makes me doubt that the people at Surge HQ understand even the most basic scientific concepts.

This is like doing a taste test between two sodas where one is clearly labeled "Coke" and the other labeled "Pepsi". It will end up measuring branding and public perception instead of anything empirical or even objective.

This isn't a measurement of search quality, it's a public opinion poll with a sample size of 250. In fact the whole thing is a poorly disguised advertisement, and I don't think it serves them well.
The problem with PHP in this case has nothing to do with types. So their reasoning was wrong from the very beginning. I suspect that no amount of "catching up" will help here, just like no amount of development will turn future axes into screwdrivers. They'll still work like perfectly good axes, though. Just like PHP will still be able to handle HTTP requests perfectly well.
I think it's the difference between Smalltalk (one word) and small talk (two words).
Mediocre – Don’t Look Up and the Matrix Resurrections
I learned Smalltalk in the Elder Days (1985). Coming from C and Pascal, the power and majesty of true collections—dynamic lists! that you didn't have to build yourself with pointers! sets! dictionaries! iteration over objects not integers! selection, rejection, injection!—was astounding. The ability to define behaviors in a generic not intensely specific way, the ability to meta-program, the ability to twiddle your environment directly—just so many world-changing innovations. Thankfully most of these advances are now baked into Ruby, Python, JavaScript, etc. (either right into the language, or with ready-to-hand libraries like itertools, more-itertools, and Underscore.js).

The image—all your code, data/state, your entire OS and windowing system, your IDE, all rolled up into one—that was an interesting approach but honestly that is the worst thing about Smalltalk. No modularity. No version control. Your image persists your data and changes forever—including any mistakes you make, knocking around inside big ball of ever-declining clarity and reliability. Over time every image collects entropy, mistakes, and bitrot like no one's business! Eventually it gets to be impossible to figure out how to fix it, or takes so much energy to maintain you won't bother. Then you have to chuck it and start afresh. Rinse and repeat! Give me today's alternative, non-persistent dev environments and version control, any day.
The vibrant leaves that you can see on trees in many of the pictures usually appear in mid-May and last until October, so that narrows it down in terms of temperature. Likely 15-25 C.
IMO it is, and usually the benefits of async Rust aren't that great for simple projects. To me the biggest annoyances is fractured nature of async libraries, you have to choose runtime and then the libraries. Tokio or async-std? They are working to fix it, but until some sort of "official" standard library for async exists it remains fractured...

Secondly adding some parallelization in normal "vanilla" Rust with std seems rather easy with channels and Rayon, so I'm not looking to retry async rust if I don't have to.
github repo:
https://github.com/Ringloop/mr-plow
All patents are on the specific implementation, but patent attorneys work hard to ensure that the claims in the patent (the only part that matters) cover as broad an area as possible.
On a personal level it's gonna be either 100% or 0%. You either got severe disease, or you didn't.

You can't extrapolate a population-level percentage from a single data point. Luckily, we've got information on hundreds of thousands of deaths, millions of hospitalizations, and billions of shots.
It's still in major use across the industry so I don't think it's too little too late. Maybe late, but not too late. I think it's pragmatism is partly why it's still so popular. No need to rush to the next best thing as PHP is perfectly capable of taking you from side-project to enterprise software with millions of users.
The last paragraph was truncated for me. I had to look at the page source to read it! Reproduced here for those on mobile browsers:

"It's a weird experience, crawling over the guts of one of the marvels of the atomic age, smelling
the thing (mostly machine oil and steam, and a hint of ozone near the transformers), all the while knowing that although it's one of the safest and most energy-efficient civilian power reactors ever built it's a a technological dead-end, that there won't be any more of them, and that when it shuts down in thirty or forty years' time this colossal collision between space age physics and victorian plumbing will be relegated to a footnote in the history books. 'Energy too cheap to meter' it ain't, but as a symbol of what we can achieve through engineering it's hard to beat."
This is a wonderful embodiment of HNs. Thanks!
We may never know if Google used their special insider access with Sonos to steal technology or not. But the optics certainly don’t look good.
The bad part is that the oceans are not just water, they are complicated biogeochemical systems that influence everything.

The oceans play a vital role in the carbon cycle due to a biological pumping action that pumps nutrients and carbon up and down. Climate change distrupts this process, it causes thermal stratification, which causes nutrition deficiency, which changes the plankton (including bacteria and algae) mix you get, which changes everything, but especially the atmosphere.

So it's not just water, our oceans are what makes Earth habitable. They are way more important than any stock market, and we should pay a lot more attention on them. All the attention really, we should just have an economy where performance is tied to how the oceans are doing.
It is true that it helps, but only for so long. I built up a tolerance for L-Theanin within a couple weeks and it no longer helped.

I chose to quit caffeine entirely and not try to suppress what my body was telling me.
Everything is an object. Being able to inspect/change running objects, etc...
> So you need to read a whole book to deploy Elixir

This isn't even remotely true. When I learned Elixir in 2016, I was able to deploy using the exact same setup as I'd used previously for Node and then Rails. This was a Phoenix app, run using mix.

Then the next day, I learned how to compile and run an Erlang release. This made deployment simpler than anything else I'd worked with previously, though not quite as easy as I've since experienced that compile down to a native binary with no external requirements at all.

Now, Phoenix even has a flag to build a docker container with a single mix command. It's not quite as easy to deploy as Go or Rust, but it's truly hard to imagine an interpreted language getting much easier.
Might be good to read the patents before posting this comment. The patents in the suit are far, far more detailed than Inc's throwaway one-line description in this article. Sonos' tech here also involves seamless automatic wireless setup and automatically assessing relative speaker volume for a given space, and all kinds of other things. If you've set up a group of Sonos speakers, versus any of the competitors, you know how much better their tech is.

It's not merely "ability to connect speakers in groups". Inc just did a terrible job here.
If you enjoyed this article but your biology background is from the 1990's or early 2000's, you might check out The Tangled Tree (2018) by Quammen
https://bookshop.org/books/the-tangled-tree-a-radical-new-hi...

It traces how we got to some of these new ideas from pre-Darwin, through Lynn Margulis, to present day nanopore sequencers via the guy who discovered Archea.
I think that says more about your particular mental model of programming than about programming in general. In the couple of decades I’ve been coding, I’ve seen good use of both dynamically/weakly-typed and strongly typed languages.

Sure— thinking you’re going to save time writing more complex applications by avoiding boilerplate is flatly wrong. However, if boilerplate would be a double-digit percentage of your code, you probably will save time avoiding it because any unlikely dynamic typing issues will be easily resolved. But if it’s small enough to be inconsequential and you’re in the typed-language zone, why not use your typed language, anyway?

Avoid dogma and use the right tool for the job, I say.
I think I'm allowed to drop down to 36 hours without any problem. Under that consistently and we run into full time classification issues and maybe insurance gets dropped.
You can, but you’d then be personally violating the patent. That’s illegal, and then you too could also be sued.
And juvenile programming language tribalism. You could compile hundreds of pages of ranting about any language and their ecosystem if you wanted to. Some people need to learn that just because you prefer one thing over the other it doesn't mean all the other things suck.

I also suspect a lot of the people complaining about X language/platform/ecosystem are not even using them in production environments judging by their very idealized view on building software.
It's not obvious at all, for wireless speakers, especially in complex multi-room setups. If it were obvious and easy, then everyone's wireless audio products would handle this as well as Sonos does. But they don't. I bought two Sonos One SLs and had them set up as a stereo pair that my Apple TV could talk to almost instantly. Then recently I got a Sonos Beam soundbar and wanted to use my One SLs as surround speakers. I expected a long, painful setup similar to what I've experienced with competing products. Instead it was seamless, easy, and delightful, and I haven't had to touch or mess with the setup at all since.

There are also a lot of details like how to handle time delays with a large set of wireless speakers so that sound is synced with a TV picture, comparative volume adjustments for a given acoustic, etc.

Did you read the patents or any other reporting on the patents or this case? For instance:

https://arstechnica.com/gadgets/2020/01/in-a-flashpoint-for-...

https://arstechnica.com/gadgets/2022/01/google-loses-sonos-p...
> why you’d consider yourself a “lowly” php developer.

PHP has always been considered as a somehow bad language in all corporations I've worked at to date. The same applies to other script languages such as python, ruby or nodejs - but PHP was the most undervalued of them all.

It's kinda strange because the language is really performant and relatively easy to use.

Maybe that's exactly why the big brain architects don't like it. They do tend to love things correlated with pointless complexity after all
BloodHound: Active Directory Analyzer
Or to anyone who uses an old-fashioned audio receiver ("amp") with wired speakers. Turn the dial, both speakers change volume. Obviously what I want.

I have not read anything besides this article, though, so it's possible the patent is being misinterpreted here.
In my experience it also depends on the worker type, if you are running sync you might need more workers depending on how much your database can handle.

Otherwise the number of workers might limit the total throughput quite severely.
Txtai 4.0 released – semantic search with SQL, content storage and more
If I'm forced to choose PHP that's the choice I would also make in most cases, probably because it reminds me of some of the things I liked about Rails.
>I am completely unconvinced by the move to asyncio everywhere in Python

Me too, now. I've just been bitten by asyncio and it wasn't nice. Running many concurrent tasks a few of which are websockets, the state of Python websocket libraries that work with asyncio is terrible. The sockets would very silently crash until I added asyncio.sleep(0) between the more expensive CPU tasks. It's incredibly hard to debug and exceptions don't get raised properly to outside an event loop, silently making your program run in a zombie state. Even stack traces instantly become a mess when you add async. Bringing something like pandas to an environment like this is probably an immense headache.
With this list you miss all the context. Apart the fact that it obviously summarizes entire comments, it feels like it doesn't represent what was said. From the 4 quotes I checked:

> is more likely to use Firefox and have 2+ google accounts

..."than the average person". Doesn't really change the quote, but it's good to know to who the average HN user is compared.

> is trained in the diplomacy of Sid Meyer's Civilization

The complete quote is: "Your average HN user is trained in the diplomacy of Sid Meyer's Civilization. Realpolitik is a joke. /s". The "/s" is doing a lot of heavy lifting here

> has ultra-secure OPSEC

This is the entire sentence (not the entire comment).
"I'm not trying to say that what happened with Bumble isn't bad, and it makes the company look somewhat foolish, but in 2021, finding the location of somebody in most developed countries, aside from your ultra secure OPSEC average HN user, is quite a simple task."

I don't think that was really a meant as a sincere description of the average HN user.
> Assuming Result can only ever be OK or Err, this is basically an Either type

Yes. It is the same concept.

SRP is rather vague, and interpreted differently depending on when and where to apply it (SRP for microservices is very different from SRP for a method).

But for the Either, or the Result, it applies perfectly. Because this thing does only one thing: it discrimates between this or that: it leaves what this and that do, are, mean etc to this and to that.

I was trying to put forward examples where the code does both this discrimination and applies the resulting meaning from it. In dynamically typed languages a bigger problem than in many others, where e.g. "null" or "some object of type X" or "a string with the error message" are far too common as return values.
If cold starts wasn't a problem we probably would have stayed with functions, and all of our non-api stuff is still on functions.
Curious, thanks for pointing that out. I mostly stop decaf at 3pm just like I did with caffeinated coffee previously, so hopefully that's not impacting my sleep.

I've lately been trying that sleep optimization thing posted here over the holidays the last couple weeks and feel like that's been helping. My fitbit is reporting pretty high sleep score for the last week, today was the first <80 in a week, and it was 79 so pretty close...
I've played with them quite a bit from the first time they were mentioned on HN. I really like OCaml. But the tooling and ergonomics are heavily in TypeScript's favor at this point, and at least for me, that makes a bit difference in day-to-day work. Anyway, my favorite of that variety of languages is PureScript. It's almost perfect.
At least we can still use duckduckgo and use the !wa bang (wolfram alpha)

Sometimes even without the !wa, as duckduckgo itself often provides the result
Sound engineers and technicians have been controlling speaker group volume for probably a century now. The Sonos patent is more than just an obvious invention. Otherwise the courts would’ve tossed it out.
> A typical Java project has way more complexity (and confusion and sadness and pain) than your typical node.js project in the enterprise world.

Personally, in my career I've seen and worked with projects in SAP, Java (Tomcat), .NET, PHP and various JS-based projects - of all these, the JS projects had the most variety of bullshit (although SAP still gets the cake for "stuff I'll never willingly work with again" simply because how mind-boggling the entire environment is).

At least it's easy enough to get a bunch of Java developers to agree on what package manager and build tool they will be using - it will mostly be Maven and that's it.

For a nodejs project, you will first have to decide on the framework to choose, then on the build tool because not every framework works with every build tool, then you will lose a lot of time until Webpack finally does what you want, and in a year half the libraries you use will be unsupported.
I haven't read the entire article, but I assume you need someone to admin the cluster?
How does the savings in billing compare to work needed for maintenance?
Solving Wordle with Basic Python
It’s Time to Close Guantanamo
I would love to see a full comparison of an API like the one mentioned in the article and full-fledged REST API (built with cacheability in mind) having something like Varnish or Squid in front.
Challenges of Remote Work and How to Overcome Them
> PHP has that whole "templating stuff" though.

That might be underestimating the feature, it was very much the core proposition of the language and likely why it's so well suited for web applications.
You know what, this is bullshit. They are making the customers pay for Google's problems. This is unacceptable, what blame do they have for the IP troubles? Google should pay, if it's deemed to be infringing, but the functionality should stay the same for the customer. Imagine this, someone coming to your house to hobble your product's functionality because another company sued the company you bought the product from.

This is proof of lacking customer protection and leverage.

I think Sonos's case is bullshit anyway, and I think this whole patent environment is ridiculous, but the approach they took to solve it is unethical.
For procedural code, async is fine. I still hate writing anything resembling a higher-order function (a function that takes or returns a function) in async Rust. The type constraints become longer than the code, and I can never seem to remember what I need to pin, unpin or box.
Subjectively, I am chilly keeping my house at 19° than at 22°. Not sure if this is an effect of thermostat placement or Nest’s algorithm for hot water rad heat (True Radiant).
The "average HN user" doesn't bother me because the adjective "average" isn't describing rigorous mathematics. It's just a rhetorical phrase.

What people are trying to roughly communicate is something much more wordy and convoluted such as... "a large percentage of HN users compared to normal percentage of random sampling of general population ..."

Constant defensive writing with endless disclaimers like the above would just exhaust readers. The tone also comes across as academic and pompous. Casual writing just substitutes all that with the more accessible (but non-mathematical) word "average".

E.g. the current HN front page has headline "PHP in 2022" and the average HN user interprets it to be about the programming language and not Primary Health Properties, a UK real estate investment trust.

We could try to substitute "typical" so we get "typical HN user" but that has the same criticism that there is no such thing as a typical HN user. True... but we can also just accept that people are just trying to communicate in a friendly way that's also concise without lawyers nitpicking the precision of every word.
But someone leads. Look around you. Most leaders are really managers phoning it in.

But when the right person with the right resources at the right time is there, magic happens. All three legs of the stool have to be there.
Oh man, finally something I can do. Irregular Snowpocalypse. Snow More Mr Nice Guy. Clear Road Turbulence. Clear Surface. So Much for Snowdays. Of Course Ice till love you (that one's a stretch). Precipitation Effect. It'll be over by christmas (that one works on its own).

There's a lot more, but I'm at work and people are walking in now.
Helluva memory this guy has...

Halfway down the article I could not stop thinking "how on Earth can he write all this from memory?"

I'm sure those engineers have a story or two to tell too... Great read, thank you.
Yes, that's exactly why I'm pointing it out. Neither Python or Ruby have(or had) that.
Open Source may look like charity to the uninformed but often it is not. Instead of being gifted, it is typically licensed.

The end result is that it should be treated like potential poison when evaluating whether or not to take it and make use of it.

A range of negative effects are possible but these usually boil down to the simple fact that users are assuming full responsibility for something they don't own, can't control and often do not fully comprehend. Included in this are popular viral licensing requirements which can invade work beyond the scope of the original entity being used.
The question should rather be: can vanilla Google Search deteriorate any further?