"close to Renault's factory in the town of Cléon", which is now preparing to start manufacturing drones for the French military, in collaboration with Ukrainian military-industrial groups.
There is nothing "rogue" about these agents. They were prompted to hack to get answers, there was a hole in their non air gapped sandbox and no system prompt that said "do not hack outside systems".
Nike's destruction over the past 5 years was really surprised and until I read up about the whole "direct to consumer" fiasco it really helped me understand another trend I was a bit confused about.
About 2-3 years, it felt like, out of nowhere everyone was wearing Hoka and On brand sneakers. In my entire life it felt like the Nike/Adidas duopoly was unbreakable, and then it felt suddenly that Hoka was everywhere.
While Hoka probably executed extremely well, I imagine it was an incredibly lucky position Hoka found themselves in when all those retailers had to replace Nike with something. Maybe even allbirds would be in a better position today had they launched 3-4 years later.
Edit: I just looked it up and it seems both Hoka and On were founded before Allbirds. Seems allbirds imploded (~2021), just as Nike was ceding all their retail space (also around 2021). Had they had another year, maybe they wouldn't have had to pivot into an AI datacenter company.
Meanwhile, I can't even get Astra to consistently re-use the same font-size across all of my HTML page headings+subheadings.
There's just no world where this actually results in a stable, respected business. It will be death by a thousand bad impressions, mistakes and oversights. Yeah, you can automate everything. That doesn't mean it's being done well.
That's not to say this might not be something feasible in 2-3 years from now, but we're still a long ways away.
There's a solution: personal liability for the executives and managers at the company, and for the investors.
For example, every person who has ever worked for IDScan at any level of management should have all lifetime compensation clawed back and then pay a further 2x of that in fines. All VCs in the company should face personal liability up to 10% of their net worth. (Fines should be based on net worth; see e.g., https://www.nytimes.com/2018/03/15/opinion/flat-fines-wealth...)
It's worse than this! You Type C-H-E then you go to press enter, and it changes the results as you're pressing it, opening the wrong thing! I've turned off all the search targets, except for applications and folders.
Top five topics per year (% of that year's projects, keyword-classified):
year #1 #2 #3 #4 #5
---- ------------- ------------- ------------- ------------- -------------
2008 Dev tools 9% Games 9% Video/gfx 7% Writing 7% Business 6%
2009 Dev tools 16% Science 11% Writing 8% Education 7% Business 7%
2010 Dev tools 8% Games 6% Video/gfx 6% Business 4% Writing 4%
2011 Dev tools 8% Games 8% Social 7% Business 7% Science 7%
2012 Business 13% Dev tools 7% Hardware 4% Video/gfx 4% Social 4%
2013 Dev tools 16% Video/gfx 10% Games 7% Writing 6% Education 6%
2014 Dev tools 12% Video/gfx 10% Writing 7% Hardware 6% Games 6%
2015 Games 11% Dev tools 10% Business 10% Hardware 8% Video/gfx 8%
2016 Dev tools 17% Video/gfx 11% Hardware 8% Business 6% Music 5%
2017 Dev tools 18% Video/gfx 10% Hardware 7% Games 6% Data 5%
2018 Dev tools 14% Video/gfx 8% Writing 6% Games 5% AI/LLM 4%
2019 Dev tools 17% Video/gfx 10% Games 9% Hardware 6% Business 5%
2020 Dev tools 14% Video/gfx 9% Games 8% Hardware 5% Writing 5%
2021 Dev tools 18% Video/gfx 10% Games 9% Hardware 7% Writing 6%
2022 Dev tools 21% Video/gfx 13% Music 9% Science 8% Games 7%
2023 Dev tools 14% Video/gfx 10% Games 9% Writing 8% AI/LLM 7%
2024 Dev tools 20% AI/LLM 17% Video/gfx 11% Games 9% Business 6%
2025 AI/LLM 27% Dev tools 21% Video/gfx 10% Games 9% Data 5%
2026 AI/LLM 33% Dev tools 22% Video/gfx 10% Games 10% Hardware 6%
The article makes a good point: JPEG XL is amazing but not specifically for the typical Web use cases, compared to AVIF. But the conclusion doesn't follow. Having an excellent and versatile format supported by browsers is very useful!
Maybe a lossless re-encoding of my website JPEGs to gain 20% size is not worth the 33% longer decode, and maybe the website doesn't need very high resolution images or more than 12 bits per channel. But my personal archives can definitely use that and it's great that such files can be viewed everywhere without specialized tooling, including served on the intranet and indeed the Web.
In summary JPEG XL easily beats AVIF on the not-so-long tail of use cases and having compatible viewers everywhere is quite useful. And with JPEG XL becoming part of PDF, it will soon be common use cases too.
As for the rest of the article: there are interesting points in the benchmark section but I think it's too early in the JPEG XL adoption cycle to draw conclusions. One thing bothers me though: There is a single picture comparison (with tag line "results speak for themselves") and I find it quite misleading: it's just picking one point on the "bytes received" line that looks best for AVIF compared to JPEG XL. Try it yourself and you'll see JPEG XL shows something already at 2KB while AVIF has nothing until 8KB, and JPEG XL looks better than AVIF after 100KB.
> It says that the government “will prioritize the rapid identification and neutralization of violent secular political groups whose ideology is anti-American, radically pro-transgender and anarchist” and “will use all the tools constitutionally available to us to map them at home, identify their membership, map their ties to international organizations like Antifa.”
So, Democratic candidates who are looking like they will win a seat this midterm cycle are going to get arrested for "domestic terrorism".
They have some nasty "dynamic tap zones" algorithm that dynamically resizes the hitbox for keys based on what it predicts you will type in order to reduce miss-taps. Anecdotally, it has just steadily been getting worse with every update. I swear I can be pressing the center of a key and it will select the next one over and immediately autocorrect to a completely different word than what I typed.
I had the pleasure of typing something on an Android the other day and it was such a breath of fresh air when it actually accepted the keys I was pressing...
It's because X is chosen (wrongfully) as the main communications channel of all kinds of important public institutions and people (police departments, city administrations, politicians, etc.).
Of course that's a real issue since the whole thing is login gated and inaccessible. But unfortunately it is the reality. So I think something like XCancel is needed.
Surveillance and totalitarian control is a downward spiral of misery and suffering for everyone, even those in power.
It reminds me of some quotes from the Tao Te Ching -
Restriction breeds the disorder it's meant to prevent (ch. 57)
The more prohibitions there are in the world, the poorer the people become. The more sharp weapons, the more the state falls into confusion. The more laws and edicts are posted, the more thieves and bandits there are.
The world isn't a thing to be managed (ch. 29)
The world is a sacred vessel; it cannot be manipulated. Whoever acts on it ruins it; whoever grips it loses it.
While it does relate to price discovery--i.e., some folks just aren't willing to pay for an additional unit of quality at 10x--my theory is that the decline in quality is another hidden form of inflation. Thing continues to cost X even though regulations have increased costs Y, ship production to China and scrimp on the inputs. (Or have market forces do that for you.)
This is the coolest thing on HN that I've seen in a minute. The whole thing is a perfect blend of ideas with the end result of something that feels... magical. Honestly this is the highest inspiration to me as a builder as I just want to create magical experiences, even if they are just small oddities.
How does this work, legally? I think that RubyGems could file a civil suit against OpenAI, but for a naïve non-lawyer reading this seems like a pretty clear cut criminal violation of the computer fraud and abuse act.
LFS takes the wrong approach in my opinion. I did it once manually over a couple of days. I suppose I hoped enduring the pain of waiting for the packages to compile would somehow make me smarter. It didn’t. I didn’t learn much. It was like following a baking recipe. I know I need to add eggs and sugar in the ratio it says but I’d be damned if I could tell you why that specific ratio works.
It’s just too much to take in at once. You start by building a cross compilation toolchain but… why? And you add the bootloader dead last, even though it’s the first thing you see when you boot a Linux machine?
I reckon a better approach would be to build it step by step, only adding new things once you’ve discovered a need for them. First you get the bootloader working, then you get it to actually load the initramfs and kernel, etc… you could even create your own extremely simple initramfs first before adding dracut, etc…
This gets you to a system you can boot and play with asap. And then you can slowly start to discover why you actually need all these things through exploration and experimentation.
