skysight-inc/HackerNews huggingface dataset:
The deprecation JEP has some discussion of why it was deprecated: https://openjdk.org/jeps/411

"The threat of accidental vulnerabilities in local code is almost impossible to address with the Security Manager. Many of the claims that the Security Manager is widely used to secure local code do not stand up to scrutiny; it is used far less in production than many people assume. There are many reasons for its lack of use: [...]"

Would be interesting to know if there were other cases besides ElasticSearch that were protected from log4j by JSM.
Musk is an excellent strategist. When he says something in public it's because he wants people to react to what he said. It doesn't mean it's true. I'm not suggesting he 'lies' exactly, more than he uses his audience to manipulate the world around him to get him closer to his goals. His Twitter account is more PR than reality.

I have no doubt he had excellent reasons to buy Twitter, but what he says they are in public probably isn't the whole story.
There are city level domains now, this question is about a decade too late
I don't wanna know the carbon dioxide emissions per person year for those. Wait, I do.
Oh, the Places Your Apple ID Will Go
Twitter alternative Hive Social surge to 1M
A <10 people startup with no Seed taking on twitter while it's at its weakest?
The error you're describing is more likely to happen with an array of ints (or really any other type without a sentinel value).

Strings specifically are often enclosed enclosed in a `while(c != '\0')` loop (assume c is the character being examined) or something to that effect, which means you'll exit at the end of the string (non-string arrays don't have this).

The CVE in question seems to be the exact opposite of this. It's that someone didn't check the bounds on a write instead of a read.
NASA's Orion capsule buzzes the moon before humans revisit lunar orbit
DEC would be an amazing story. They invented pretty much everything, forming the fundamentals of many now-dominant IT companies. They also underwrote some of my favorite educational programming growing up. Would be nice to see a little more 'Sponsored by Microsoft' for my own kids.
It unsurprising how you went from "could potentially scale to 1B users -- and nobody could stop it, this is new" to "of course it cannot scale, but this is still new"

So what exactly is new, and how can it scale?

Note: for a newbie Glitch and Itch are infinitely more scalable, and more innovative.
Thirded

Or Get Tailscale in the Windows Store so it could auto update for all the endpoints out in the wild I don't control (company laptops, users home PCs, etc). Trying to get TEN people to manually update today was a pain, I can't imagine even triple that.
I’ve always liked the pattern of putting timestamps on any objects in my DBs.
> As long as nothing changes, and you don't run out of disk space (from logs for example), things stay working pretty much just fine.
> ...
> There are other things that can bring a site down, like security issues, or bugs triggered by unusual states, too much traffic, etc. But generally speaking those things are rare and don't bring down an entire site.

Aren't these changes inevitable, though? There is no such thing as bug free code.

Another thing that forces consistent code changes is compliance reasons- any time a 0-day is discovered or some library we're using comes out with a critical fix, we would have to go update things that hadn't been touched sometimes in years.

At my last job, I spent a significant amount of time just re-learning how to update and deploy services that somebody who left the company years ago wrote, usually with little-to-no documentation. And yes, things broke when we would deploy the service anew, but we were beholden to government agencies to make the changes or else lose our certifications to do business with them.

Eventually, Twitter will have to push code changes, if only to patch security vulnerabilities. Just waiting for another Heartbleed to come around...
You can control your computer's software but not Alexa's. The internet doesn't record your home via microphones and submit to FBI:

https://techcrunch.com/2018/11/14/amazon-echo-recordings-jud...
Related: https://www.japantimes.co.jp/life/2022/09/30/style/industria... (https://archive.md/oVyQZ)
https://archive.ph/Crrhj
Please Restore Our Registers When You’re Done with Them
I think Twitter was stuck in a not-especially profitable niche. They shift into fast-mode to get out of it and find a better spot, then they can shift back into stable mode once they occupy a better equilibrium.

That said, there are lots of bugs in Twitter now, today, when they presumably had the benefit of being in stable mode for a long time. For example, Twitter regularly refreshes and loads new tweets while I'm reading them, pushing the tweet I was in the middle of reading out of view. That seems like a pretty silly bug to exist in a mature product. I regularly reach a state where I have to kill the app and relaunch it because all of the "back" commands just minimize the app instead of taking me back to the timeline. I could go on.
The query cache was behind a single lock. Thus while fast, it serialized all DB operations. And the more CPUs you have the slower the performance. Especially since any write has to go through the cache and invalidate all affected queries.

It was meant to accelerate PHP code in the 90s with single core CPUs. It was never designed to be scalable and in-development (back then) versions had already disabled it, which gave me the idea that it was something to try.
Very few people are going to be converted to paying users if they start to see downtime or breakages. No one buys into a failing app.
> Sure, you can run the platform with 1/10 headcount with significantly degraded user experiences (say ~98%). This is not a problem for startups but people usually have higher expectations for established companies.

This exactly. During the recent Whatsapp outage, many threads popped up on HN about how big of an issue this is in Europe, since Whatsapp is the main messaging platform in Europe. Thankfully, these outages are short and far between, so they never actually cause real issues. This is obviously costing Meta/Facebook a lot of money, but allows them to be an essential service. So essential in fact, that every major news outlet in my country sends a push message as soon as Whatsapp is down.

If Twitter wants to be a comparably important platform, they need that same stability. And Twitter, for me, is very much the best place to stay up-to-date on any current event (in near real-time). Reddit used to be pretty good with Live, but that's pretty much died (and was mostly a summary of tweets anyway). I really hope Twitter survives Elon, because I don't know of an alternative right now that has the same value in this use case.
> This bot likely had low priority and that’s all

If it was a prerequisite to land $100M ARR from all the media properties’ marketing budgets to advertise the multi-billion dollar pipelines of the movie and entertainment industry, that lil’ bot was the gate to $11,415 per hour of revenue at risk if its uptime failed to sufficiently please the attorneys and auditors from those customers.
closer to the end of the game, even water will make most participants confused
Alexa-powered does not necessarily mean Alexa devices made by Amazon though.

For example: I own a multiroom speaker setup not made by Amazon that is Alexa-enabled, all speakers could run Alexa if I had set them up for it (which I won't, ever), and they're very likely counted on this metric. I can remember a multitude of other speakers and devices with an Alexa-enabled badge on their packaging that aren't made by Amazon.

It'd be good to have hardware figures for sales of Amazon's own devices.
Sure, but they're called smart contracts because they're meant to literally codify an agreement.

If you just want to trigger actions based on something and then store it, you don't need the machinery of the blockchain.
They all do stuff like that. It'd be really nice to have a button to turn that off entirely. I never want a device to literally read me long-form webpages. Stop trying to LARP as a Starship AGI when you aren't one.
This article doesn't support its claim. It references an article that claims Google asked managers to rate a certain percentage of employees as poor performers. But the claim that Google intends to lay off these poor performers seems to be totally unsubstantiated.
I'd second the Kidder book. It's really the story of the people building it, and how their lives were impacted.

I'd like to suggest a larger project: a history of the features we've come to call a "computer". For example, the stack. The PDP-8 didn't have one. Programmers would roll their own in software, usually with the limitation that you could only have 1 level of call, because you only stored one return address.

So; what machine gave us the first hardware version of the stack? When did using a stack become the job of the designer, not the programmer? As far as I can tell, the first one was the Burroughs B5000. In fact, I'd wager the B5000 architecture pretty much set the standard for all computers that followed.

But I think that story would be really interesting. As long as it's not only about the tech, but about all the people who tried, and the one(s) who succeeded. Not just a single feature, but the set of features that we now consider to be required for a "real" computer.
My concern was how will putting these little languages together work and it turns out that the author also had these questions.

Where do we draw the line on "enough DSLs" for example? And what happens to the gains from using several DSLs in tandem as opposed to a high-level language with libraries that accomplish the same thing?
Well, that's Central North Americans for you - still reeling after the 9-11 attacks and looking hard for revenge, however unjustified, and thus easily manipulated by politicians and the press.

In the UK and AU, the two principal partners of the "coalition of the willing", few in the public felt the situation justified and the bulk of those with exposure to global policy, military intell, travel abroad etc. definitely felt it was a bogus war.

Tony Blair was all too aware the supporting intelligence was thin and inadequate at the time - which came out in followup Royal Commissions(?) (they had a big UK inquiry into the matter), and John Howard (AU) was happy to play along despite a lack of backing from ASIO et al on the intel as it was a treaty obligation for AU and not pushing back gave leverage for other US-AU deals.

Altogether it was much less a coalition of the willing than it was a tagging along of the bribed.
> I’ve become convinced that “little languages”—small languages designed to solve very specific problems—are the future of programming,

Yes, but over time very specific problems become bigger/different problems which the little language isn't ideal for, the original developers move on leaving someone new to figure out the problem and language which is probably poorly documented and very brittle. Application developers probably aren't suited to writing and maintaining language code.

The only caveat is an external system provided with its own language - like RDB/SQL - which is proven and well maintained - but its hard to call SQL a little language.
I think that matrix is a good tool. It is objective, and it does seem "the least you can do" - so in other words if you tick all the boxes you are doing OK, and if there are some missing that is definitely stuff to work on. Excelling would be to go beyond the matrix. And I think this is how the matrix should be.

I sort of hate that we have to define it so formally, and it would be nice to think "she's a good dev" and that instinct is it. But in reality a benchmark is needed to be fair and prevent bias.

In addition to be a good engineer you need to code, and coding tests are a way to find out. Ideal ones would be open ended, plenty of time, and with the interviewer "searching for success" to try to counter interview nerves. "Oh yeah I made that mistake I should have done XYZ" is as good as getting it right first time.

In an ideal world there would be some standard basic coding tests to avoid fizzbuzzing everyone. Sort of like AWS or Azure certifications, but for actual coding, that are respected, as a base level. Do them once every 2-3 years say and that is your passport past some useless interview stages. But I digress!
There will always be those that think that Twitter can be written by a single programmer in a day or so. How hard can it be for such a simple idea after all, given that there are hundred of tutorials producing a version in just about every language just a search away.

Keep it running? One part-time should surely do it?
Tmobile
They were one of the first users of Mesos, but they didn't create it.

> Mesos began as a research project in the UC Berkeley RAD Lab by then PhD students Benjamin Hindman, Andy Konwinski, and Matei Zaharia, as well as professor Ion Stoica.

> The social networking site Twitter began using Mesos and Apache Aurora in 2010, after Hindman gave a presentation to a group of Twitter engineers.

https://en.wikipedia.org/wiki/Apache_Mesos
https://en.wikipedia.org/wiki/Jaywalking#United_States
While I agree with the idea that journalists in general were not nearly critical enough, it’s a bit much to say that no one ever asked questions and/or was critical. I vividly remember the interview in which Matt Levine participated, and he basically called SBF out on running a Ponzi scheme and being OK with it (which was then, surprisingly enough, acknowledged by SBF).

To make this all about “telling it like it is like we do on the trading floor” is trying to force an angle that is simply not there. The better point hidden in the article is that journalists don’t really grasp the material they’re covering, and as such are incapable of asking critical questions.
That's true. It will definitely mitigate different category of exploits out of the box, but you still need people to acknowledge and be intentional about their decisions.
Reminds me of Moloch, the packet capture and indexing software[0]. I wonder why it was renamed and moved out of the AOL github org...

[0]: https://news.ycombinator.com/item?id=22949604
wasn't intending to be whatabouts. just pointing out that the tournament has a long history of this kind of stuff. it's not new. it might be TIL for people unfamiliar with the tournament, so feel free to pile on and beat a dead horse. as the saying goes, there's no better zealot than a new convert.
I don't think you would call it dead, just a failure at the original objectives.

Its the greatest and most successful rube farming exercise in history, which is...not nothing.
Looks like you need to me a member of tilde.club and get ssh access to their server, then you can just echo to it:
https://tilde.club/wiki/quilt.html
Right, I forgot the US is a backwards country where the people worship corporate profits.
Blinkenlights go all the way back to ENIAC, where ping-pong balls were used to make them more prominent.
Yes, many countries that aren’t the US provide health insurance regardless of your employment status.

Some countries (Germany, Switzerland, maybe others) will pay employment insurance even if you quit of your own accord and lower the elimination period if you had reasons to do so (as certified by a MD)
Goodness, what kind of process/tools did you use to track that problem down?
The reason why Twitter hasn’t crashed is it’s well written and well orchestrated. Once a bug comes in and crashes something that is when the chaos starts. It’s almost a guarantee that the current crop do not know how to fix the bug. It will be interesting to see how they handle that.
I think that without code push they won’t be able to maintain compatibility. With updated APIs from third parties, new hardware, new encryption requirements from clients or browsers etc. It’s a slow descent into chaos indeed.
Based on the recent disclosures it seems that any new security issues pales in comparison to the current ones.
This is also true for lower numbers. It evens out so each player is equally likely to end up with each number.
It is more that it tends to beat raw deal for the purple who lose their jobs for no good reason. The Twitter people will likely mostly land on their feet but most leveraged buyouts aren't affecting highly compensated employees with highly in-demand skills.
Well, it happens very rarely (I don't cry unless whatever I'm having is extremely good).
When it happens, people find it quite amusing, and it usually starts a conversation about the pleasures of life.
Yes, TikTok is very addictive and an unproductive time sink, and that's why Meta is trying to make Instagram more like TikTok, and Google introduced YouTube Shorts to try to replicate it. Digital Fentanyl? Probably, but the fact that it's a Chinese company it's irrelevant, since American companies are trying to replicate it and they wish they were the first. Now, is it a net negative for society? Of course it is.
I can believe that a dozen talented engineers could in principle suffice for Twitter.

But who believes those 12 engineers still work there? The author of this specific item is in fact not there any more.

And a lot of other people are needed to bring in revenue, don't you think? Nobody is paying for a beautiful caching system.

It's like if I doubled my weight in the last ten years. Half of me is bloat, and yet, there is no possibility bisection will improve my health.
Fabrice Bellard is a robot from outer space - this must be the only explanation.
2 preschool kids here. The two things that get played with over and over again are the play kitchen and all the food items etc that go in it, and the dress ups. Number one toy over the lst few years has been a Melissa and Doug wooden ice cream set - https://melissaanddoug.co.nz/products/melissa-and-doug-ice-c...

It is a bit more expensive but they use that all the time. And every kid that comes here spends time playing with that thing.
I can hardly get my coworkers to understand one language well.
> I would love for you to experience the boarding process so you can get a feel for it, and the social stigmas around it too which is where I think you could get an answer to that question. Maybe watch an FPV youtube video of a traveller using the service and take note of the line to board and disembark, take note of the entry way and the luggage area and think about how it would all work with a bike.

Q: How does it work for passengers in wheelchairs?

(That is a genuine question, I was recently travelling by tram in Basel, Switzerland, and along with another random stranger pitched in to assist an elderly woman in a wheelchair who was struggling to board, partner wasn't strong enough to manage on his own. The tram doors were nice and wide, but given the height difference between the tram and the platform, a ramp sure would have helped...)
No. This is him backpedaling on all the shit he's said and done because advertisers are stopping ad spend on Twitter.
> IRL he seems so introverted.

He uses Twitter non-stop, and has an incredibly curated public image.
Types of VC Bridge Rounds: 0x, 1x and 10x
They are paying for the privilege of the direction of their wise new overlords, I suppose.
I think the opposite. Many softwares at its best when the team was small. Software companies have to hire many people because it needs to report growth to investors, headcount is one of the measurement of growth. It is not necessarily good for the product, actually many times, it hurts the product, but overall it is good for the company, the company will enter new areas, can explore new things.

What Twitter is doing is to scale down first, focus on the product, and once it gains traction, it definitely can scale up again. I don't think it will hurt the product very much.
Ah yes, the "no true cyan" fallacy.

Kind of like our music system isn't actually harmonic, we've just learned to accept the small error (distributed evenly across notes, called equal temperament). But you try telling the masses they're actually listening to garbage, or getting musicians into just intonation and mathematically pure harmonics. It's impractical.

Similarly I fail to see the success in debating how truly cyan this or that tech can produce. It doesn't seem to invalidate my point of RGB being an old "invention" (of evolutionary process).

#00ffff is cyan. The fact that almost all devices fail to reproduce that color exactly is an implementation detail.

Fun trick, you can oversaturate your receptors by intensely staring at max red for a while, then close your eyes, and my understanding is that this perceptual illusion lets one briefly observe pure cyan.
The real problem with sales management systems are crossed incentives: The value of a sales person is their exclusive knowledge and contacts so nice voice interfaces to the knowledge vacuum hose are not going to make a change.
> But given that NTP (either ntpd or chrony) tends to give me an estimated error of around (tens of) 1e-6 seconds, and PTP can get down to 1e-9 seconds, I'm not sure how many data centre applications need that level of accuracy.

I know that in trading, auditing trades / order books requires extremely accurate timing, and they typically deploy GPS hardware to get the required level of accuracy. As GPS is accurate to a level of 30ns, 1e-6 to 1e-9 (1ns) is exactly the kind of improvement needed to not need GPS hardware anymore.
It’s not a problem IMO. Bicycles aren’t very useful vehicles compared to cars, which is why a very small share of the US population uses them on the roads in the first place. Unfortunately that tiny minority of people are very outspoken about attempting to socially and physically engineer the world to cater to their preferences.
> cut corners on actually verifying the subscribers

Did they actually verify anything other than the ability to pay $8? It seems wild to me that they thought it would work out just fine
Your data is about "percentage of female names in whole population".
I'm talking about "most popular name to assign to newborns".
Sorry for misunderstanding.
> Tangent but I do hope that Musks trim down results in orgs that have less “executives” and a layered cake of a org structure, and more autonomous small teams that execute on shared overarching initiatives.

The core problem is that this approach doesn't really scale out because communication overhead exhibits quadratic growth to the orgs size if it's untamed. The feasible options are:

1. Let the complexity bring chaos across the org
2. One decision maker rule them all
3. Gives some sort of management structures to the org

Your proposal is somehow between the option 1 and 2. The option 1 works pretty well for smaller orgs and it might scale to a quite sizable business if the members are generally competent so org-wide trust can be well-established. But anyway you'll hit a road blocker eventually since people cannot spend all of their time on communication overheads. The option 2 just moves the burden of entire complexity into a single personnel so it's not really a reproducible solution but more of a mere luck.

Hence the option 3 is the only remaining option for regular orgs and many smart people tried to figure out the best structure (or at least best practices) but unfortunately we don't have a definitive answer yet. Google-style "tech level" is one of the tool to reduce communication overhead by setting a common structure for expectations (e.g. "we have 1 L6 and 3 L5s to take that project" is generally easier to convince than length explanations of your team members). It's not ideal but it somehow works so it's adopted.

You're likely right that you'll be much more productive if you can get rid of those bureaucracies, but getting other folks convinced is a completely different story. Trust takes time to propagate and people have a limited time to spend on it. This obviously could be drastically simplified if you can work with Elon (or similar style leaders) directly but his time is extremely limited so there will always be only a small number of people who can enjoy that privilege...