skysight-inc/HackerNews huggingface dataset:
Right, the name or any kind of lineage does not matter, Wayland is the X11 successor because it is the current seriously developed and improved open display protocol. Nothing about Wayland stole from X11, has any less legitimacy to be the post-X11 protocol than something called X12, or prevents anybody else from improving X11 or from working on an alternative they call X12 or anything else.

I don't know why people get so hung up about this. People including its creators may have been over-optimistic about Wayland, but it was never going to be a case of a weekend hacking binge producing something useful out of the gate (X11 had that distinction because it was entering a very small and very green field). X11 has been used for so long because it is very well supported, robust, and has been extended and improved for decades and most of the remaining problems it has are very hard to solve. And that's exactly why we also didn't see something called X12 happen overnight either.

The fact that Wayland has been created and worked on and blessed by a number of X11 alumni did lend it a good amount of credence early on, and one might say gives it the right to be spiritual successor to X11. But really if you censor the names and look at the practical reality rather than sentimentality, Wayland creators and developers have been going down the long difficult road of coming up with something better and nobody else did, so that is really why it is the next X11. Progress may seem slow but it does not stop. Features continue to be added, implementations continue to improve, support continues to expand and its takeover seems almost inevitable at this point.

Someone might mention "network transparency" at this point. As far as I've seen from the outside looking in that was never the fundamental requirement of the protocol as far as I can tell. Non-transparent protocol like DRI were never not considered to be X11 by the X11 architects and developers who wrote and merged them, showing they have always been quite willing to step out of rigid dogma and embrace practical application. The original X announcement never said the project was a network transparent window system, it said it was a good-but-not-perfect window system and if a good windows system today does not require network transparent protocol (because users don't care as much as they did back then or because networking can be achieved at other layers) then there is no reason it couldn't be X12. The X12 page linked here enumerates some other X11 features that could be dropped too, I've never seen a reasonable argument for why a network transparent protocol is the be-all and end-all of X.
X11 cannot handle the average user connecting an average laptop to an average external monitor (no usable per-screen scaling). Maybe this was good enough in the 80s, but today it is seriously holding back the platform.
Sure, but the end result is that nobody can host a service with an ipv4 address only. You would be missing out on the majority of your audience.
A related one I like is “vonundzu” which I guess you’d have to spell as “fanencú?” I’ve never seen it spelled, but it’s dismissive slang for aristocrats both real and self-appointed.
The Minds of Spiders, Octopuses and Artificial Intelligence
https://archive.is/Xleoa
It exists only as a patch from Intel (https://github.com/intel/cartwheel-ffmpeg/blob/master/patche...) but I haven't seen any efforts to upstream it yet.
Great write-up! One extra detail that might be worth including in the block device/storage section is that Firecracker doesn't yet pass through discard (trim) from guest to host (as fallocate(FALLOC_FL_PUNCH_HOLE) if file-backed) like qemu?

The fast/efficient asynchronous io_uring backend now in released Firecracker makes it a good alternative for full-sized VMs as well as the original short-lived micro-VM use.
Have you considered https://github.com/squint-cljs/squint ?

Personally I couldn't let go of Clojure's other advantages but at least using the syntax would let you step off the syntax churn bus
Well, now we know this Supreme Court isn't really "originalist". The concept of a national security exception exists nowhere in the Constitution. Nor does "executive privilege". These concepts were invented in the early days of World War II.[1] They do not go back to the Founding Fathers. Mostly, they go back to an arrangement between J. Edgar Hoover at the FBI and the Attorney General in 1954.

[1] https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2226404
Just out of curiosity, what extensions do you need for your day-to-day use?
COW (Container on Windows) that escaped the Silo
The beauty of the English language always comes from picking the word with the perfect connotation.

At the most articulate, you have speakers like Christopher Hitchens: “It especially annoys me when racists are accused of 'discrimination.' The ability to discriminate is a precious faculty; by judging all members on one 'race' to be the same, the racist precisely shows himself incapable of discrimination.”

― Christopher Hitchens, Letters to a Young Contrarian

But sometimes the strongest turns-of-phrase in English can be the simplest. We were recently chatting about the Portuguese "Cansas-me a beleza". In English, if you said to someone: "You tire my beauty" with perfect delivery it would be withering.
It's near red infrared. It's like saying that blasting red light to your face, will have health consequences.
The average user has a laptop with an Intel or AMD iGPU. Gaming machine are niche.
I have been a KDE user since 2010. I've started this habit a few years ago that every time I upgrade my desktop distro's release, which is twice per year (first Kubuntu, now NixOS), I try out the wayland mode for a while, until I find the bugs to be too annoying. A few years ago I switched back after a couple of hours. The last time I tried I remained there for 3 months. So yes, a lot has improved, but I'm still back on X11.
Copying the how is ok, but copying the why it’s not.

The problem here is not how companies react to a downturn, but why they think there’s one. And they are copying the whys too.
> If it ever becomes a liability, you just check in the "transformed" code and it's gone.

I've done this and regretted it - CS transpires to ES3 and specifically null chaining is completely unreadable.

From a backend perspective it's no biggie to instead keep the CS dependency and gradually convert files manually when you have to make changes anyway, or when you have 15 minutes to spare between meetings.

You become fluent enough to not even need tests after a while (yikes!).
> The very first arcade game with a CPU was Midway’s 1975 port of Gun Fight.

Cool, I used to have a portable clone of that game: https://www.cnet.com/culture/80s-handheld-game-still-hits-th... The glowing VFD had a certain mistique that the by then more common LCDs lacked, and the game itself was really fun, either against the CPU or against another player. And it played the iconic "funeral march melody" when your gunslinger died, which has been stuck in my head ever since...
Interesting. Suggests that we should not admit refugees from brutal civil wars?
Well, most providers worldwide still use IPv4 which means that cost of switching to IPv6 is higher than cost of maintaining workarounds for 10 years, and who knows, maybe it will be the same for another 10 years
> until you think about it for ten seconds.

It's not about the number of seconds that matter, but it's the direction of where your thoughts go.

I hear this expression often and I don't think it's fair; it's quite condescending. The fact that you think something is obvious and if only somebody bothered really thinking about it for a moment it would be obvious to them too, is missing the reason different people come to different conclusions about things. What you think next is determined by many factors, including your goals, your biases, your prior knowledge, what you had for breakfast.

And you should know that, if you think about it for ten seconds.
China's first ChatGPT-like software to be made open source
probably should hire 10,000 more people, the AI race is heating up
I mean, the amount of solar irradiance is directly correlated to the amount and activity of sunspots, which have increased steadily at roughly the same rate as average global temperatures.

It's not even something that you need secret mystical knowledge that only the woowoo anti-climate-change wonks believe in, you can get the data and do the maths on it yourself.
Have you got a few million quid to recertify equipment?
65 days ago I bought a brochure titled "How to get updoots easily: a confessions of karmawhore"
The boom and bust cycles are artificial and are created entirely by the central bank. We can have continuous stable development and did have it when the gold standard was still a thing.
It has been Good Enough™ unfortunately. At this point I feel like we will never see IPv6 fully deployed.
I also found it useful to have a link bind that just focuses the link element, often that can open up hover menus or trigger other focus/hover CSS changes.
> You also should have the entire development environment segregated from the "business" corporate network as well.

This is the key point, otherwise you'll also just get a linux machine with developer root access, but EVEN CLOSER to the corporate network.
Anyone who believes that XFree86 was stable in 1999 was apparently running a different XFree86 to me. The sysrq key was mostly useful at the time for using the SAK shortcut to kill all processes on the current terminal, which with luck included your wedged XFree86 which would then get respawned by xdm. I don't miss those times.
> In the short term, we'll focus on building creative and expressive tools. Over the longer term, we'll focus on developing AI personas that can help people in a variety of ways. We're exploring experiences with text (like chat in WhatsApp and Messenger), with images (like creative Instagram filters and ad formats), and with video and multi-modal experiences.

I guess that makes sense. It works great with their metaverse vision (and might give it the USP it desperately needs), while bringing short-term benefits as well. I wonder what they mean by text in WhatsApp though? A chatbot for companies to paritally automate all the business that now happens over WhatsApp, or a text-mode Alexa, kind of like XiaoBing (which far predates the current GPT craze, but is now much cheaper to create)?
X11 is not usable for everybody without preconditions though.
> most important asset

talk is cheap.

Action reveals true intentions.

And tbh, anyone who believes that they will not ever be laid off (and only ever voluntarily quit) is delusional. Whatever a company claims - "you're like family", "important asset", "valuable talent", etc - nothing compares to cash and profit. The shareholders do not suffer losses to prop up a business or employees.
> have some well paid, high I.Q people running them

Unfortunately even well-paid and high IQ people have been known to cut corners and take risks. Look at the space shuttle among many examples.
Concrete hellscapes is certainly a treat to freedom. They are designed to extract value from humans efficiently, while the end beneficiaries of this madness wisely choose to live on private islands, around the nature.
Yea, that's true - in the sense that it's "chilled", or "cool" (i.e. a frisdrank) but not in the sense that it's cold (koud) or chilly outside.
Well I'm wondering. It seems mastering linguistic inputs does give you access to some kind of generality.
Typically you have (1) an ML model to generate embeddings from the items in your db and (2) vector support in the db to order/compare those rows by similarity (i.e. cosine distance between embeddings). So this just gives you the second part in a more convenient / efficient package. That's super cool, but only the second half.

For the encoding model, you could use any ML model you want, from cheap/less complex models to expensive/incredibly complex models like GPT-3. You could even use a face recognition model to encode face images and sort/compare them the same, etc

So this just makes it a lot easier to roll your own similarity systen with an encoding model of your choice plugged in. If you have a lot of data to encode and aren't afraid of running your own model, it is a great part of a solution. But it is not an all-in-one solution.
VMware's Bitnami starts packaging apps for Graviton and Ampere
Lots of cringy posts here. It was obvious a lab leak was the most likely. It’s useful that so many people discredited their intelligence by making outlandish assertions to the contrary, often going so far as to accuse anyone who disagreed as being in various ways substandard persons. These people seem to want to double down. A foolish consistency is what I expected, but it’s still pretty funny to read these comments and see the mental gymnastics.
A commit is also a sequence of commits.
Wayland is default on several distributions and has some pain points, much like X did in 1999 (it had many back then, and in fact still does today). But it’s definitely usable, it’s my daily driver here.

The main difference is in 1999 X did not have real alternatives, so if you wanted a graphical desktop, you had to fix the X bugs period. Here if you don’t want to deal with wayland issues you can fall back to X. It makes for slower development…
Apparently it does, positive ones!

https://news.ycombinator.com/item?id=34609625
licensing for a non-free closed-source platform
Is it possible to mount video for Youtube using only ffmpeg for cutting footage, adding music/letters/filters and never using GUI?
> subscription to a friend, partner, therapist etc

that might be pretty cool actually. I tried a couple of shrink bots pre-chatgpt, they weren't very good back then, but I think with enough effort it might be possible to get them to a mid-level human shrink in this latest iteration. FB owns tons of conversational data to train on, too!
Chuck Norris once opened Windows and created the Macintosh.
Dilbert sure seems popular lately
Even you're in a team, same thing happens. Which causes the illusion of "seniority" when you think you're experienced.

It's not. Most of the time, you're debugging messy code. It's not the experience one might want to accquire. It's like ad-hoc knowledge.

Lone developer or not is not the issue.
I wonder how hard it is to add more decoders to it? It'd be great if it could cope with .m2t timecode from HDV video streams.
How do they separate cases to get the research? I mean, isn't it more likely that overweight people consume more zero-calorie sweetener...

How do they conclude the increased clot production isn't just a variable of the study groups population? Like, how do they know that weight or lifestyle of the population studied is a lurking variable?
Also to quickly convert video formats and containers, scale and crop renders, alter speed, make gifs
That is simply not true.

For example:
There are, in fact, known risks to near-infrared radiation exposure. Erythema ab igne, for example, is a disorder characterized by a patchy discoloration of the skin and other clinical symptoms. It is caused by prolonged exposure to hearth fires, and it is an occupational hazard of glass blowers and bakers exposed to furnaces and hot ovens (e.g., Tsai and Hamblin 2017). It is not a risk to the general population, however, in that the irradiance is usually many times that of solar near-infrared irradiance.
because it's dangerously stupid to let an AI hallucinate commands on your cli that could potentially destroy your files or system
> YMMV. When it reaches the level of X11 that "just works for everyone without preconditions" it will become usable in my coordinate system

I don't think X11 ever "just worked" for me. Every computer I installed Linux on had X11 problems.

The XKCD about Xorg.conf was very relatable back then: https://xkcd.com/963/
I can imagine paranoid HN users filling their shoes with gravel to avoid big tech surveillance
Are you claiming that black people are dangerous but that they can be fixed or that black people are not dangerous and so there's nothing to fix?
The network effect is so huge it trumps on everything else.

I'd like to use pijul. I can't because I work with other people. Can I use it when I'm not working with other people? Well I can, but why should I care about a tool that better handles merge conflicts if I have nobody to conflict with?

Some tools are more sensible to others to the network effect.

We already are slaves to the network effect even for tools that we don't technically require being the same as the one your colleagues you, let alone those that do require that.
The tiny diamond sphere that could unlock clean power
I've read somewhere else that Apple did not participate in wide lay-offs which means they play their own game and don't fire what they recently acquired. Hence it makes sense that other companies have worse big picture and outlook capabilities.
First Law of Thermodynamics Breakthrough Upends Equilibrium Theory in Physics
Shipping a fallback doesn’t mean the alternative is not in daily use.
According to this stackoverflow post, the quote is probably made up: https://skeptics.stackexchange.com/questions/18236/did-ralph...
I think part of the "problem" is Amdahl's law.

When you're solo developing, the laws of physics are different when it comes to code quality and refactoring. The scaling of the cost of technical debt is different depending on the size of the team.

In a team, large refactoring efforts are slow and difficult to do incrementally. The best way would be for one guy to lock the mutex and just go, come out however much time later with something cleaner.

If you have 10 people waiting for a week-long refactoring of some central aspect of the code, that's 1 week put in and 9 weeks of work put on hold. It's so inconceivably expensive it's usually not even an option. So instead the code must stay squeaky clean at all times.

On the other hand, if you're just one guy and nobody is waiting for you, it's that would-be impossibly expensive big-bang refactoring task that cost 10 weeks for the team is 1 week of work like any other.

If the primary outcome is not the code itself, but the software it compiles into, I think you're an absolute fool if you don't lean into this as a solo dev. You can be so much faster than a team dev. You can code dirty, cut all manner of corners and fix it later if and when it becomes an obstacle exactly because large code base changes are on a massive discount.

Although as the article notes, it's difficult when the team of 1 grows to more, or the project changes hands, as the solo dev may have known all the weird jank and how to fix it, but the new developers won't. That said, refactoring is cheap, so as long as there's not been an busses involved, a hand-over is very doable given some preparation.
In my experience it's more often the other way around.

Most projects I've seen with actually readable code and a consistent overall structure have been written (mostly) by a single coder, of course usually with contributions from others, but not real 'team work'. Of course there are also messy projects by single authors, and readable code bases by teams. But in the latter case: the more the responsibilities are spread, the messier the outcome (IME at least).

I think in the end it comes down to the experience of the people involved.

And then of course there's personal taste, one person's readable code is a complete mess to another.

In any case, the post reads like the author stumbled over one messy project written by a single author and extrapolates from there to all other projects.
Shouldn't RHLF help with this? So it learns that when people specify a number, they mean something very specific.
Most security cameras would not have an IR filter, for the sake of the ability to record at night with IR illumination.

Even for those that do, IR filters are rarely perfect, so a bright enough IR light would still do the trick.
Exactly, there's hundreds of lines of illegible X configuration for every such "just works" setup.

There's a difference between "the community has learned to deal with it" and "just works".
The "f" mode in Vimium is just wonderful. I wish that I could have a system-wide keyboard just like that.

I seem to remember in Windows 7, there was some sort of voice assistant, that could similarly put a label on every visible clickable element. That was for voice command, but would be great for keyboard navigation, too.
I've often noticed developers seeing a project for the first time and not long after proclaim it as "bad code" and that it needs to be refactored or rewritten (with zero thought as to whether it's good for the customers or the business.)
Oh God, that = this made my heart jump a little. Is this what it's like to feel old? :)
Indeed, that's the point I'm making. Very often (not always, but much more than most people would think) the 'quick' solution that people are suggesting will not actually be any quicker to implement than the 'right' solution, and if you chased an illusory short cut, you end up with a timeline that is no better and an architecture that is worse and either forces future work onto you or slows down your future work or saddles you with a bunch of unnecessary maintenance.
Implementation looks dead simple for this too:

$ = (f, x) => f(x)
flip = f => (x, y) => f(y, x)
|> = (x, ...fs) => fs.reduce(flip($), x)

However, |> in typescript is quite hard to type (no recursive types). The best approximation you can get is to manually insert

|> = <A, B1>(x:A, f1:(a:A)=>B1)
|> = <A, B1, B2>(x:A, f1:(a:A)=>B1, f2:(b1:B1)=>B2)

At that point, a simpler binary function will make more sense

|> = flip($)

And tsc will interpret the types in the pipe more correctly. Of course, the compiler can allow functions to be called without parentheses to avoid a macro for pipe calls, which will bring our definitions to

$ = (f, x) => f x
flip = f => (x, y) => f y x
|> = (x, f) => (flip $) x f

It might also help to add a simpler function composition function too, as it will greatly help reuse without requiring you to write lambdas

$ = (f, x) => f x
flip = f => (x, y) => f y x
. = (f, g) => x => $ f (g x)
|> = . flip $

It could also help to remove those pesky parentheses from lambda definitions too, maybe with simpler declarations like `f x y =` converting to `f = (x, y) =>` and enabling automatic currying:

$ f x = f x
flip f x y = f y x
. f g x = $ f (g x)
|> = . flip $

But, have you noticed that we mostly have binary functions? We could greatly improve readability by making our "modifier" functions (aka combinators or adverbs) into operators. So civet could implement a special syntax for operator definition, and then we would write for definitions like

($) f x = f x
flip f x y = f y x
(.) f g x = f $ (g x)
(|>) = flip . $

(Oh wait, does this look like something else?) So we would be able to express `console.log(Object.keys(data))` like

data
|> Object.keys
|> console.log

or equivalently

(console.log . Object.keys) $ data

without having to special case for pipes! But more importantly, if you enjoy the Clojure method of piping, you can define

|>> x f ...fs = f ? |>> (f x) ...fs : x

which would give you the syntax you like. And I have a feeling the types will compile just right in a language that looks like this...
True but ability to read and understand code will be as important as ever: maybe more important. Your job will
be perpetual mini code
reviews!
No it's higher because they've started charging for IPv4 addresses, they don't want to lose their cash cow...
I used Vimium for a while, mainly for the feature of opening links with the keyboard. But I never stuck with it, forgot to use it, because I really don't like the mode-switching and having it default to taking over keyboard input.

Finally found Link Hints, which does only the link opening part, but better (IMO), and with normal keyboard shortcuts. Now I'm constantly using it.

https://addons.mozilla.org/en-US/firefox/addon/linkhints/