skysight-inc/HackerNews huggingface dataset:
In 1989, I got a IBM AT, with VGA. I flipped from a Herc card, with 25 lines, leaped past EGA 43-line mode into VGA 50-line mode. Turbo Pascal, and SideKick ( or psychic ) all ran perfectly. Paradise VGA w/ 512k. Sony 15" Trinitron, very sharp. Why don't other people program in this?

Wideprint had a 132 column mode for Lotus 1-2-3, and again, SideKick jumped in perfectly.
There's a LOT more to it, but I'm not prepared to talk about it for a number of important reasons. There will be a book coming out eventually, though.
I guess it's like this – implement interfaces, and common code comes with it when you inherit (then override to modify behaviour). A common interface really should have common code so this is appropriate. What is wrong is to inherit from an object with a different interface just to get your hands on the code - that might seem obvious but when OOP started to be used in industry, that was acceptable or even recommended practice. That malpractice was formalised away by Barbara Liskov with the Liskov principle. I'm pretty certain you're doing the right thing already so it was a clarification rather than a criticism.
On windows and Linux this works great. I have two Dell business screens, one with USB-C, a DP in and a DP out. Just connect another screen to the DP out, and you get two screens over one USB-C connection. Together with the charging and USB hub provided by the screen this replaces a docking station for me.

However, Macs have spotty support for this. I believe it works on the newest Mac books, but not older generations, and not the Mac mini?
Yeah, I think something like this would make sense. I get why people might not like it, but this is what we’re dealing with whether we like it or not.
Don't know about the United States regulatory frameworks, but in Europe, building hydro power, or big wind farms for that matter is getting hard too. Both with local protests and regulatory requirements.
It's a non-starter because people disagree on "simple".
Okay, if you want to be pedantic, 1.3% of all CO2 emissions come from gas flaring (500 Million Tonnes annually on roughly 37.15 billion tonnes of CO2 emitted). Seems like a lot to me at a time when we are meant to be reducing all greenhouse gasses. It might be better to build power stations near these shale deposits to reduce coal and use this resource rather than pollution for no gain.
SeaMonkey is an independent project allowed to use Mozilla infrastructure. Thunderbird is funded with user donations.

What is serious revenue?

Google and Microsoft are betting AI will be very relevant to web use. And what amazing and edgy features would Google and Microsoft be unable to match?
You might want to add some more info, such as, are you talking about birthing assistants?
That and the fact that web is built over a language for text, not UI. HTML is a terrible foundation for UI.
I think Go creates a false sense of “getting things done” by allowing too little abstraction and increasing LOC. The writing/thinking ratio is great, but most of it is having to write 4 lines of repetitive code for every reduce that should have been one line instead
What does the contract you agreed with when you bought the original domain say?

No-one can comment on the "legality" of your agreement without knowing what it is.
Sekhurity.

Can't have user-programmable tools, because they could be used to ship (gasp!) malware, or let users (GASP!) work around policies of their employers' IT staff.
I won't call this kind of programmer good or bad, IMO this is just the result of 2 factors:

1. This specific person leaning towards being a contractor rather than employee. They are more focused on solving technical problems and improving technical skills, but not learning the problem domain, their company's business model and organisational structure.

2. Never being personally accountable for the result of their work, because the company takes teams/departments accountable, instead of individual people.

Number 1 by itself is not a bad thing. Number 2 will be fixed as soon as this developer works for some time as a real contractor or if the organisation gives him a 1-man project and holds him accountable for it. After that they will learn to make sane technology and architecture decisions.
I think it's completely orthogonal issues, no? You probably refer to OLEDs superior black levels etc. But this thread was about subpixel rendering. One can be bad while the other can not. It's unrelated.
But a[i] > 0 can still compile to a branch, depending on the compiler.
>Isn't "movement in bed" how all sleep monitors work?

No.

The best ones monitor your brainwaves, and the best wearables monitor the next best ting, your hear rate and blood oxygen.

You can get knocked out by drugs, alcohol or just die in your sleep from apnea so you'll not move around in bed and your bed motion sensors are useless.

You need to tap into the body's vital signs to know your sleep stages accurately, especially REM.
I wonder how difftastic would handle a paragraph that got reflowed via a gqip command. Would it show almost every word as changed or only the changed words and ignore the fact that many others now reside on different lines?
I guess in that they don't offer a reproducible toolchain they are proprietary blobs, but it is functional software with an open license (Apache)

I do think its noteworthy that the time between something becoming available as a python import and the time it takes to integrate into production tools is apparently > 1 year.
I agree it's not faster, especially when using a simple WM with no animations.

However, I also find it easier to recall where I was looking by moving my head between static content instead of having it change.

FWIW I use a 32" screen positioned so that I barely need to move my head to see it all, and try to have all things I'm looking at visible at the same time.
People are notoriously bad at identifying what actually led to their success. Career advice authors even more so.
Delphi was even better. Great IDE, great language, compiled executables.
Too bad that paradigm didn't survive the web.
A unikernel designed specifically for running WASM apps and compatible with WASI
The author was on a mismanaged project and his takeaway is to blame his fellow devs rather than hold management accountable. In fact, he does not even seem to recognize the existence of a managerial issue.

This whole article reeks of imposter syndrome. Of course, it must be the case that all the devs who are more productive and impactful than the author are actually secretly very bad, and that the author's inability to understand technologies like Rx, validation and testing frameworks is actually a hidden strength because it makes him some perfectly interchangeable lowest common denominator developer. I hate/hated working with Rx, but it is fundamentally not challenging or complex.

This story is common because the types of people who are capable of single-handedly building large parts of a software product in a short time are naturally the ones who are "hyper-productive" and leveraging a tonne of different technologies and paradigms. The unexceptional "slow and steady" devs are usually not capable of having that kind of impact. When devs like the author do manage to single-handedly deliver entire codebases (e.g. over long periods of time), they are typically just as bug-ridden and unmaintainable as what the "rock star" devs produce.

Ultimately, the onus is on businesses to avoid crutching themselves entirely on a single developer's output. But there are a heap of shitty businesses that have no method for delivering software other than to let singular, highly motivated and passionate developers "go HAM" on the codebase with no oversight. These businesses deserve to fail, and the unmaintainability of the code base after the departure of their key players represents the correction of a market anomaly.

>Then suddenly, the frontend lead quit for greener pastures

What does this even mean? Key personnel do not "suddenly" quit.
On a side note, when I had my startup and was the CTO, a lot of advice I got and also what I ended up realising was that my priority and goal was to build an amazing `Tech Team`.
> Even though I take pride in my ability to adjust my opinions in the face of new evidence, it can really hurt, and it sure did this time. Now what should I believe? And what fragments of false belief were left behind in my mind? On top of that, I had to notify the people I gave the book to. When there are that many errors in a single chapter, who knows how many there might be in the rest of the book? It was clear to me that the book could not be trusted.

I think these are great questions. I say believe nothing. If you verify something, now you're getting closer. Personal experience is also the golden source - I do not dismiss it as 'merely anecdotal' - its actually the only thing of which it can be said "I know!"

> I think we should demand a lot from institutions and very little from individuals. Humans can be lazy, selfish, biased and greedy. They can also be also hard-working, altruistic, fair and generous. But the dark side of humans isn't going away any time soon. Institutions, however, can do a lot better than individuals. (The scientific community is an example of such an institution — despite individual scientists' many imperfections, science keeps progressing.)

And here I disagree. I don't demand from other individuals. But nor do I demand anything from institutions. In fact - I demand less from them! What are institutions except grouped individuals, only now with many opportunities to avoid accountability, and many incentives to do whatever it takes for money?
I tried to google as well (like another commenter), I did find a lot of 1:1 ratio screens though; I wouldn't mind that I think.
Not yet compliant, but working on it. There's quite a few ASIL-D components too. We don't use GCC but rather tip-of-the-tree LLVM. Embedded is a completely separate and different mess using whatever the vendor ships for a particular microcontroller.

So far our safety guys haven't seen any issues with tool qualification besides requiring everything to be documented and the whole system to be re-tested in case of any tool changes.
Git’s defaults are no good for prose. Can’t make line-by-line comments easily and the default diff is worthless for paragraphs.
Few things make me more furious than the constant „computer says no/knows better“ one has to deal with on so many occasions these days, be it mobile apps, websites or other
Difficulty & cost evolving the interface between microservices can seriously hinder improving the actual product.

I've seen the misguided adoption of microservices affect a couple of companies & products.
32" 4k = 137.68ppi.
27" 1440p = 108ppi.
24" 1080p = 91.78ppi.

Significant difference. 32" 4k is not pleasant to read natively, and bringing it that close that is would be readable means you are putting things out of your focus and you need to start moving your head a lot.
I think you're right to be skeptical that microservices are required in order to stop code becoming spaghetti.

I think of it as all about what kind of boundaries you choose to put in your code and where. https://hivekit.io/blog/mesolithic-architecture/ The blog calls it 'mesolithic' architecture, but I almost wonder if 'gabion' architecture might be better - separate small rocks held together by a metal frame, forming a single architectural piece.

The principles of good architecture do not require you to make your boundaries network or process boundaries, but they do require that you have boundaries and that you're careful when and how you cross them.
Could you expand on this a bit? How’s the ergonomics, window management, etc?
It's not an argument against government spending, nor was it intended as one. What makes you think so?

It's an argument against this specific argument for government spending.

Making bad arguments is excessively easy, independent of whether the thing argued for is good or bad, or true or false.

To give a simple example: consider a faulty proof of Pythagoras' theorem. See eg https://www.cut-the-knot.org/pythagoras/FalseProofs.shtml

Pointing out flaws in these purported proofs is not an argument against Pythagoras' theorem; it's still true after all. It's merely an argument against the faulty arguments.
>maybe Vimeo or a newcomer

I feel that Nebula was supposed to fill this slot, but failed. The clunky UX being chief among my complaints about it, otherwise it just seems to generally lack in content variety and appears to have trouble attracting new creators. I want to like it, but I just can't find a good reason to.
What big language features did Rust get in the last few years? What big changes have you seen that changed codebases directly? Cause I code in Rust and my Rust code these days looks very similar to what I was writing a few years ago. The biggest change to the language was async/await, which was introduced almost 5 years ago.

What if you compare it to Go that fairly recently got a massive new feature that can change how you write code drastically, ie. generics?
It depends on the stand really. You can get VESA compatible monitor arm and rotate as many degrees as you like.
> These [unintended consequences] include: decreasing overall inclusivity; dehumanizing; including people who should be excluded; being imprecise, inaccurate or misleading; and disembodying and undermining breastfeeding.

Describing the wrong groups, and being misleading, are exactly what I am not advocating for. I have, sadly, seen people advocate find-and-replacing in a document to make it “more inclusive”, and that never ends well. (See: https://en.wikipedia.org/wiki/Scunthorpe_problem) The majority of phrases criticised by that article are… awful. (Seriously, “gestational carrier”? “Pregnant” is already a noun.)

> “8 in 10 people” will get pregnant after having unprotected sex

Obviously you don't use clunky language constructions, and you certainly don't do that. (If you are, I dare say that's not the only problem with your writing.) But one doesn't stop being a woman at menopause: this ambiguity might cause clear communication for some, but it comes at the expense of unclear communication for others.

For accessibility, you can't have a one-size-fits-all text.[0] There's a reason we have separate easy-read versions.[1] Provide an imprecise, oversimplified summary if it improves outcomes, but don't make that the only version.

> They may not know, for example, that “a person with a cervix” is a woman and refers to them

If people don't know what the cervix is, explain what the cervix is, probably in parentheses. Rather than constructing an artificial example, I'll quote the World Health Organisation (https://www.who.int/news-room/fact-sheets/detail/cervical-ca...):

> Persistent HPV infection of the cervix (the lower part of the uterus or womb, which opens into the vagina – also called the birth canal) if left untreated, causes 95% of cervical cancers.

This sentence could do with some work, but it demonstrates the point. A skilled writer can be clear and correct: it's not either-or.

[0]: https://indoxicate.me/text-accessibility-requires-multiple-f...

[1]: https://designnotes.blog.gov.uk/2021/10/11/easy-read-is-hard...
You could do two column layout that way too, because nobody should write more than 80 characters wide.
MeeToo, Denmark is a little too far away (9 timezones…:(
The marital example is something I came up with, but not actually sure if that happens as I haven't gotten married myself. But it sounds something like that would exist so you can react to someone faking your identity and registering a
fictive marriage with someone in your name.
Read it, and similarly, it seemed to have all the hallmarks of some takedown more motivated by a quest for notoriety/popularity that any systemic failings in academic literature review.

It's an airport pop science book for goodness sake, it's not like fabricating results to get an article in Nature.
I don't see anything special in having tens actions on a UI item. Toggles, action links and vanilla buttons would take care of it.
The irony of a blog about software performance going down after being on HN for 2 hours is too much. (I know, it’s just Wordpress, I’m just being a grump.)

The archive version seems to be missing the branchless versions of the algorithms - is that missing from the article itself as well? It’d be interesting to put the different versions into compiler explorer.
Former Aston Villa manager Steven Gerrard encounters challenges in Saudi Arabia as Al-Ettifaq concedes a last-minute goal, extending the winless streak. Despite a strong lineup, the team faces scrutiny, and Gerrard pleads for reinforcements
Passing arguments as read-only references does impact the purity of functions from a fundamentalistic view point but, as you experienced first hand, is sometimes more or less required for performance.

Looks like your FP zealots didnt learn how to compromise on that point or how to work with constness in general.
There’s a little “tall poppy” syndrome in this article. The two hotshot engineers who are the villains are clearly out of step with their teams, but their teams sound like they might be conservative clock-punchers who resent the existence of any new technology which might require them to grow a bit.

The two attitudes represent extremes, and most people will be in the middle. I’m the agitator on some projects, and I’m the voice of caution on others.
The main problem seems to be really poor process.

They told or were willing for their leads to start building stuff out on their own. The rest of the team were "slacking off because business requirements were in the works".

They had no review of what the leads were doing. They did not involve the rest of the team in the design and build of the frameworks. The leads, also in the absence of firm business requirements produced highly abstract systems that could cater to many different requirements. The rest of the team couldn't understand it and it was bug prone (and presumably hard to debug).

I assume that these frameworks had to be ready by the time the fabled business requirements were finally produced, so there would be some time pressure to deliver them.

I have no idea whether the leads bear much responsibility here from what was written. I do know that the way they write software is very likely to produce this kind of result.
> Copyright is not a moral right, it's a monetization strategy that enables some information related business models at the expense of others.

The reality is actually more interesting than this post.

The US Copyright Act of 1790 was meant to provide an incentive to authors, artists, and scientists to create original works by providing creators with a monopoly. The monopoly was limited in order to stimulate creativity and the advancement of “science and the useful arts” through wide public access to works in the “public domain.” Major revisions happened in 1831, 1870, 1909, and 1976. Source: https://www.arl.org/copyright-timeline/

As to moral right, from Wikipedia: "Modern copyright law has been influenced by an array of older legal rights that have been recognized throughout history, including the moral rights of the author who created a work, the economic rights of a benefactor who paid to have a copy made, the property rights of the individual owner of a copy, and a sovereign's right to censor and to regulate the printing industry. The origins of some of these rights can be traced back to ancient Greek culture, ancient Jewish law, and ancient Roman law.[2] In Greek society, during the sixth century B.C.E., there emerged the notion of the individual self, including personal ideals, ambition, and creativity.[3] The individual self is important in copyright because it distinguishes the creativity produced by an individual from the rest of society.[citation needed] In ancient Jewish Talmudic law there can be found recognition of the moral rights of the author and the economic or property rights of an author.[4]"

https://en.wikipedia.org/wiki/History_of_copyright#Early_dev...
And maybe CTO means “the founding programmer of a new startup” in which case my advice would be to stop reading and start coding :-)
My dream monitor is a 22” 4K monitor. I searched it for a decade and this creature just doesn’t exists. There have never been a single 4K monitor under 27”.

The only thing that somehow could do the job would be iMac’s panels but I’m just not interested in an All in one and I already have good enough computers.
"undergraduate" appears here as a disparaging adverb?

Academia showed me that freshmen arrive green and wide eyed, but also
filled with integrity and wondrous belief in science. Only after
graduation, masters, doctorate and postdoc are they fully ground down
into cynical, jaded, institutionalised husks. Before they have
learned to play "institutional games" undergrads are the kids who see
when the Emperor has no clothes.
Do Androids Know They're Only Dreaming of Electric Sheep?
Haven't found any replacement, but dashcam.io looks very promising for that use case, will definitely be checking it out!
Once more, a Java programmer has a bad time writing Java and scapegoats Haskell.

> One day, these twerps pushing this stupidity of “copy everything always cause ‘it’s easier to reason about dawg’” are gonna get theirs.

Making defensive copies is literally item 39 of Effective Java by Josh Bloch.

The Haskell way is to not bother with that shit, because you don't have to.
> Compared to what Apple makes off hardware and service revenue

Really I wish people would wake up and stop with this bullshit.

Do the other manufacturers do anywhere near as much R&D as Apple does ? NO ! (2023: Lenovo 2bn vs Apple 29bn).

Do the other manufacturers maintain their own OS across multiple hardware platforms ? NO !

Its easy to sit in your armchair and spout crap about "well, Lenovo does it !". Well, the OS on your Lenovo is Windows or Linux. And the parts in your plastic Lenovo are almost certainly 100% off-the-shelf commodity parts.

Meanwhile Apple's R&D is what brings you, for example, the unmatched Apple Silicon chips, which everyone except the die-hard Apple bashers agree are genuinely industry leading.
Datafun: A Purely, Total Functional Datalog
>The only thing that imho can come from this sort of arguing, is the kind of religious divide, evangelism and proselytism that ultimately only hurts both sides of the argument, because it makes people favor dogmatic choices over considering what's actually useful in the current situation?

Of course :-) I'm not advocating for it in anyway. Quite contrary. That's just what I've seen - which sadly is, that tons of developers are not able to rationally discuss architecture and the just default to dogma.

Often someone dropped stone tables years ago and they just follow. If instructions they were given were simple and well understood on mechanical level, usually result is bit better than total chaos. Thus black&white approach.
Some turbine facts for reference

For a typical onshore wind turbine, the tower can contain approximately 295 tons of steel

The concrete footings are usually 9 feet thick and 60 feet in diameter, requiring about 300 cubic yards of concrete, which is equivalent to 30 to 40 truckloads.

The blades have a 20 year lifespan and cannot be recycled, being made from fiberglass reinforced with plastic, also known as glass fiber reinforced polymer (GFRP). With newer ones also incorporating carbon fiber.

All that said, for a turbine to produce enough clean electricity to offset the carbon emissions produced during its manufacturing, installation, and maintenance, is typically around 7 to 8 months.
I still miss the simplicity and power of the Lightspeed/THINK IDEs for Pascal and C.

For me Metrowerks was a big step back in terms of complexity, speed and affordances.

The thing that I loved about MPW was MPW Shell and Commando, brilliant if you compare it to the state of the UNIX art at the time, probably tcsh, and still to this day feeling just a bit like the future.