skysight-inc/HackerNews huggingface dataset:
Maintaining old systems and not getting the chance to exercise your hottest take on how they should be rebuilt is often tedious as hell. But I find a lot of comfort in it. I usually find that the future road maps that stick in my head for a year or more are the ones worth a 10-year overhaul, and I like to be able to tell clients that when enough of their stack is reaching end of life, we should do this major rewrite but I already am fairly certain they won't have to do it again for another 10 years. e.g. I have yet to deploy any production code for a client running on Nodejs, but I've written enough dependable systems in it on my own free time in the last 5 years that I think I might now finally advocate for it under certain circumstances, knowing the strengths and weaknesses.

It does help - as you point out - to be in the position where the non-tech company will almost always take your advice if you tell them they need to change platforms. But the most effective way of getting yourself in that position is to prove that you exercise that option only when it truly is in their best interests.
I have about 20 nRF52840 boards deployed around my house for various automations.

Personally I've found that for casual experimenting and software development, the official nRF52840 DK board is your best bet. Here in the US it only costs around $50, and all of the samples in the nRF Connect SDK support it natively. It's also pre-wired for power measurement.

My first board was the nRF52840 MDK from makerdiary. I ordered it from Amazon because it was cheap and it had one-day delivery. Most of the NCS samples do not support the makerdiary boards as-is. You can usually add a dts .overlay file to the sample to get it working, but it will take a bit of extra effort. Having to tweak device trees right off the bat adds another step to the learning curve and makes it harder to try out random sample apps.

Over time I migrated to using the DK for development (the integrated debugger + serial interfaces are super handy) and then using the USD $10 nRF52840 Dongle boards for deployment. I program the dongle boards using a knockoff J-Link probe from Aliexpress and run them off battery power. I eventually stopped using the makerdiary MDK since it didn't really fill a niche for me. But YMMV.

One nice thing about the board in this article is that it has an external SPI flash, which could be useful if the nRF52840's 1MB onchip flash isn't large enough for your application. I use A/B partitions to support OTA updates and it's pretty easy to run over 512kB per image if your use case is moderately complex.
No, it's not. The Altamont wind farm on hugely expensive Bay Area real estate can power under 50,000 homes. For comparison a coal or nuclear plant of 1/1000th the size can power 1 million homes. You are not factoring in opportunity costs. The price of land is real and it is not cheap.
Isn‘t that a problem of shareholder thinking? A problem that imo should be meanwhile singled out as a bad way to handle a company. Shouldn‘t it be handled with thinking of all stakeholders? This would result in better management decisions, or not?
> I like seeing all the tooling artifacts at the top level when I open a GitHub repo or something, it’s nice to see at a glance - like a quick digest of what is used to develop that software.

I agree with this proposal that it can be a mess, but hiding the files or directories isn’t a solution. Instead, the mess we often see reflects the abysmal unification of tooling in modern software development, and the JS ecosystem is perhaps the worst offender.

If things suck, let them fester in the open air. Stuffing them away isn’t gonna fix the mess, just sweep it under the rug.

I must say though, that one huge pet peeve that I have, is software that don’t allow projects to be rooted in a subdir of the git repo root. This is a huge annoyance when you work with multiple stacks in the same project.
AFAIK Facebook never supported RSS, more’s the pity, nor Twitter. A big part of the pathologies of Facebook come from control over the feed prioritization algorithm, which means it favors their interest, maximizing “engagement” and thus polarizing content. This goes away entirely if you use a RSS feed reader with your own prioritization and filtering.
> With XML, it failed because something like JSON was much simpler.

I remember when XML was pretty new and I used this new-fangled technology called XML-RPC. XML-RPC was amazing and I was using it to connect desktop applications to web applications. If you go look it up, you'll notice that bears a striking resemblance to JSON.

But what technology actually took off for RPC in XML? SOAP. And SOAP is a nightmare of complexity and hardly works right the first time between heterogeneous systems.

It's funny how much people want to add complexity to the JSON ecosystems with the same over-engineering that killed XML in the same space. Luckily the design of JSON is such that it resists that kind of complexity and also because XML exists it takes a bit of that load.
Fukushima Daiichi was built in just 5 years and see how that went.
Have you seen Musk swimsuit photos? There is no way he's 200 pounds. It's much more and it's not from muscle. He'd have to hardcore diet and train to get back somewhat in shape.
They only didn’t count people falling from the roof as cost of solar energy. For a country of 40m inhabitants, it’s about 1 per year, and that’s huge:

> Solar: In an average year nobody would die – only every 50 years would someone die.

It’s like saying Chernobyl only caused 32 deaths because the other ones were outside the plant.
Hard to imagine how to design such study: (close to) 100% of people that adopt kid WANTED to have kid, and planned for them. Some XX% number of people having kid via pregnancy wasn't planning for them, and some even smaller YY% number doesn't want the kid at all.

Not to mention that unless the adoption of kids are done blind by parents, there has to be some biases there. As an example out of my ass, kids with behavioral problems might have way less adoption rate, and potentially those are the one with below median outcome in any case.
We use XSDs to generate JSON Schemas. The schema converter also generates code to convert JSON files to XML, so we can use our existing XML infra while we migrate.

As you say both can be used to validate input and to generate typed code.

However I find the XSD design tools better, so I expect we'll be doing the XSD first approach even after all our integrations are JSON native unless something radical changes there.
His 36,500 charge cycles is pretty impressive as well.
Hey, I never checked before, but you seem to have 1.0.0.0 answering pings. That's awesome.
You can purchase access to phone numbers for the purposes of verifying accounts. While phone numbers are a method to prevent easy sybil attacks, it is not effective when dealing with a determined actor.
Because language is one thing and community is another thing. I have the same feeling about Crystal.
> Throwing your fifty config files in a hidden subdirectory is what's typically referred to as "supporting dysfunction".

Hilarious expression. But we’re going even further here: standardizing dysfunction.
I agree that it's dull but the fact that I still know ColdFusion 20 years later gets me a lot of work. No, it's not Silicon Valley money but it is Fairfax County money, which ain't bad.
> If the EU were smart they would fund a nuclear company where all countries can bundle their resources and expertise

A bit like the EPR design?[0]

Unfortunately it's not really the poster-child for efficiency.

[0] https://en.wikipedia.org/wiki/EPR_(nuclear_reactor)
May we rephrase this as "Office rents are finally easing and will hopefully stay sane until 2040" ?
> This suggest it is not technology that's holding us(US and majority of EU) back, but bad project management practices. We too could have a new plant built in few years.

The US demolishes any and all of its state capacity anytime a company calls the congressman they bribe to complain that the government doing (insert project here) intrudes on their right to make money. That’s the difference. The Navy has been running nuclear power plants underwater for 50+ years at this point, but having a state organization that builds and maintains energy infrastructure would compete with all the existing energy sector interests, so it can’t be allowed to happen. Contrast this to China, where businesses do not have authority to override the state and this difference is obvious.
As an Ansible person, I couldn’t agree more. Being able to manage variables at basically any level of precedence is extremely useful.

I am also ever more deeply concerned about IBM’s hell-bent purge of all the good left at Redhat. I had thought it would take them less time to destroy Redhat, but I’m sure they wanted to make sure they spent time “listening” before making all these ecosystem-eroding changes.
Show HN: ChatGPT summary of HN frontpage streamed on Twitch
Consume a ChatGPT summary of HN frontpage on Twitch.

Please follow the channel if you like it, it will motivate me to put more time into this.

TODO:
- Improve Audio
- Improve UX
> With XML, it failed because something like JSON was much simpler.

No. XML was introduced as a simplified SGML subset/profile to become the base for new markup vocabularies on the web; both SVG and MathML were specified using XML (and later integrated into HTML 5). The intent was also to replace HTML by XHTML.

The idea to introduce service payloads as custom, non-UI XML and then transform those payloads into XHTML was induced by XML, but distinct from it.

However, W3C went crazy with SOAP and XML (and RDF), attempting to establish entirely new and unproven paradigms such as XForms with XHTML2 rather than merely simplifying syntax, which was bound to fail, and laid ground for browser vendors to evolve HTML outside W3C.

Then XML heads somehow felt insulted, refused to change course or learn new things. Most even didn't realize XML is just an SGML subset, and that everything that was possible using XML is by definition also possible using SGML (plus handling HTML and markdown and a couple other things making SGML more complex compared to XML). To this day, we're hearing XML heads dogmatically advertising their overly strict and verbose red-headed stepchild of a markup language, and wondering why nobody wanted to bow to XML. The article is about this kind of people who want to use their tool under all circumstances, project requirements be damned.
NASA’s Hidden Underground Bunker [video]
After years of struggling with a NAS from a well known manufacturer, my solution is a 2012 Mac Mini. I replaced the internal 2,5" HDD with an 8TB SATA SSD.

Advantages:

- extremely reliable

- completely silent

- low power usage

- all in one (no external drives, no external power brick)

Disadvantage:

- no longer officially supports latest macOS
Except we don't have that nuclear capability and it takes decades to build lots of new nuclear capability during which current projections indicate we'll instead deploy lots of wind, solar, and storage, outstripping any new nuclear capability by an order of magnitude or so. The reality is that most projections (even the pessimistic ones) get us to net zero around 2050-2060. Most of that is driven by renewables. I'm actually hopeful that more optimistic scenarios are possible because of continued improvements in cost of renewables and storage which would enable faster rollout for less investment than currently projected.

If people find a way to drop the cost of nuclear by an order of magnitude to finally deliver on its potential, I'm all for it. Great stuff otherwise but it's just too expensive currently.

In short, I don't see that happening any time soon. We might actually get fusion before that happens. And we shouldn't be betting on that either. It might happen, it might not happen. Either way, we need to get rid of fossil fuels. Right now wind, solar, and batteries are looking pretty good in terms of mass production and deployment of new capability. There's a gap with nuclear and it's widening rapidly.

Most of that is cost driven. It's just a lot cheaper/faster/better/less risky/etc.
Hah. That sounds like my dream job. A software company that's not controlled by VC, not burning money, actually shipping a product, and (presumably?) turning a profit... that's an actual unicorn these days...
> "based on particular conditions at the construction site or other local circumstances" [..] happening precisely because the US does not have much expertise in this area that leads to exorbitant costs

Umm, the sites are the sites.

We're going to somehow attempt to leverage our one standard design and rule out the very existance of any local circumstances by adding enough expertise?

Good luck with that.
I product I developed in the early 2000's used that technique for a dynamic tree control. That product wasn't retired until 3-4 years ago. It still worked as intended in modern browsers but you could, in theory, fire up Netscape 4.0 in 2019 and that dynamic tree would still work.
not going to read it. i know how it always ends up:

"men suffering...women most affected"
It is the support for narrator.device that amuses me. One of the most futuristic feeling things an early Amiga was capable of doing being attached to GPT. It would mimic an actual 80s tv/movie impression of the future of computer interaction.
I would like to see a graph of 'budgeted expenditure' vs 'overage costs' for large construction projects so that we can see on what level this is 1) true of any large project 2) any significance
Renewable and nuclear are not very compatible when they share a grid. For two reasons:

* Nuclear requires an extremely expensive initial investment that needs to be recouped. For that to happen, the finished plant needs to make as much electricity as possible. This means ramping down a nuclear plant because the sun is high and there's a steady wind spinning all the turbines at max capacity for the next couple of days makes zero economic sense. This is the reason why nuclear powerplants in the US don't even really have the technical means to reduce their output. They are designed from the get-go to be run at 100% capacity, always. And while this argument holds for all powerplants, the economics of nuclear are cut so close, they risk becoming a net loss at current electricity prices if they are ever forced to throttle down. Even if you run them 60, 70 or 80 years.

* Even if you build your reactors in a way that allows them to be run at reduced output (the French did that, you obviously need this capability if your entire grid runs on nuclear), doing so is complicated and requires many reactors to work in concert. The reason for this is technical: if you significantly reduce the output of a nuclear reactor, it poisons its own fuel rods with radio-isotopes that make any significant increase in output impossible for tens of days, sometimes for over a month. So if your nuclear reactors do grid-following, you need 30+ of them to take turns, reducing output one night and recovering for a month afterwards while the other reactors take turns doing the same.

The exception to that is of course hydro. Nuclear loves hydro, they complement each other perfectly.
This is a huge problem, and I lack the faith that it will ever get fixed. People have talked about it for years, and the amount of investment and research is nonexistent compared to the talk about it.

I have met many people in my life that virtue signaled using this issue. I opened to them assuming it was safe. They used any vulnerable moment to amplify my pain for their own enjoyment.

It sounds insane, but this is a fundamental(could be instinctual) aspect of human societies. Look at prisons. Look at war. Look at how online spaces react to men vs women.
Pumped hydro is actually possible to be a lot smaller and less ecologically devastating than traditional hydro.

The requirements are rarely for more than a few hours or a day or two of storage, which significantly reduces the required reservoir volume. And the only requirement is that it be at a higher elevation than the source body of water, so rather than disrupt an entire river and its migration patterns you can have it off to the side.

Because the sites are now a lot smaller and not limited to drops in elevation along rivers, you now have many possible sites; many pumped storage sites are either existing reservoirs or disused mines.
Let me give a more recent example.

A few years back I was building a B2B website for companies to manage event listings[1], fully modern React stack.

I wanted to get the backend API up and running first so I threw together a prototype in WinForms and C#. I had been writing React all day every day for a couple years at that point, and I hadn't used C# or WinForms for quite a few years (3 or 4 at least).

Also none of the GCP APIs I was using had official C# WinForms libraries (hah!) but of course everything had nice React integrations.

So anyway, within a day and a half or so I have a C# desktop app up and running that has about 80% of the site's planned functionality implemented. It is ugly, but it works.

Over 3 months later I have the React site up and running.

The React site supported Mobile and Desktop browsers, and it looked nicer, but the productivity to create the React site was literal orders of magnitude less.

FWIW I had a similar experience going from React to Svelte, I got done in 3 days what would have taken me weeks in React.

(For those paying attention, Svelte was still slower than C#!)

Part of the difference is that we expect web apps to be all shiny and work at any screen size with fancy CSS, vs a desktop app which can just do its thing.

The other part is that, IMHO, HTML+CSS are crap for laying out application UIs. Better than what they used to be, but still absurdly complicated.

[1] Create their business profile, list and manage events on a timeline/calendar, view attendees, send announcements to attendees, real time view of people as they show up to the event by hooking into Geo-locating on the phone, manage photos, and so on and so forth.
But what amount of realism is accepted? If the result is still in the uncanny valley, is it OK? How far can we dig out of the valley before it becomes not OK?
> What's wrong with therapy? You go to the doctor from time to time to take care of your physical health, why shouldn't you go to a therapist from time to time to take care of your mental health?

There's a big difference, though.

Doctors, by and large, diagnose using a body of knowledge acquired from scientific fact backed by intensive peer-reviewed and reproducible studies. They prescribe using a similarly evidence-based foundation of facts.

Therapists (psychologists, not psychiatrists) have no such foundations in science. Much of what they "know" is from non-reproducible studies.

If you need mental health maintenance, there's literally no evidence that going to an actual therapist is any more or less helpful than meditating, religious involvement, sports clubs, homeopathic remedies, diet modification, acupuncture, etc.

I'm not arguing that taking care of one's mental health isn't a good thing, I'm arguing that there's no evidence that therapy with a psychologist is better than the placebo.
They "forgot" the word "spectroscopy" which changes the meaning of the sentence.
Yeah, this resonates. The times I have been vulnerable in relationships has always been met with, exactly as you say, recoil and disgust. It's a really shitty feeling to feel clingy and unworthy... in other words, when you actually need someone by your side.

As men, when we need people the most, that is when they are nowhere to be found. A stark contrast with women, who naturally seem to support each other in such times, and aren't hung up on the social stigma that encumber men.
The X in AJAX is there because the devs had to put it in MSXML, because they couldn't add it to IE itself due to a code freeze, and because XML sounded cool back then. https://web.archive.org/web/20170424220609/http://www.alexho...

While there probably were some pages using XML in AJAX, many were just sending HTML fragments.
Yes! But whether it will pan it is up in the air. There are only 2 plants operational right now. Once there are 1000 or something like that we can see whether this approach really works to scale up to tens of thousand.
Seattle is already mostly hydro, so building solar there would be a bit silly
Too late, renewables have already reached parity output with nonrenewable options in some jurisdictions. And wind/solar has proven its cheaper/cleaner than digging Coal.

Nuclear fission facilities are a subsidized loss-leader 1950's technology.

1. No one wants the waste, and every dump has leaked (erasing these off google maps doesn't unpin the Geiger-counter net downstream)

2. No one wants to live near Reactor facilities cooling ponds

3. micro-reactors and the like... are fools errands that ignore the costly reality of securing the life-cycle of these facilities.

4. A $7B Fission facility could also equip every home on a distributed infrastructure in Texas 7 times over. Many homeowners are getting non-subsidized solar themselves, as they realize they will end up paying for the same boondoggle centralized projects.

The AstroTurf and scientific hubris is not enough to pass off this technology as sensible. Nuclear power only makes sense for deep space probes, the north pole, or a large submarine.

Have a wonderful day =)
The mac doesn't use ctrl modifiers to use copy paste. If you remapped Alt/option and windows/command keys on a windows keyboard alt-c & alt-v (i.e. the keys to the right/left of the spacebar) would be recognized as cmd-c and cmd-v on the mac. PyCharm supports a windows and linux keybinding that lets you use ctrl-c and ctrl-v to copy paste but the mac generally uses the cmd key as opposed to the ctrl key. If you want to use ctrl-c and ctrl-v you can remap both of those pretty easily using karabiner elements to cmd-c and cmd-v.
It does seem a little lazy and jarring to quote from ChatGPT, but technically is much the same as if he had added a named quote directly: "Merriam-Webster dictionary defines character as.." or "Albert Camus once said that character is..."
Compared to all other basic materials we use in our life, lithium is pretty mundane. No war has been faught over cobalt. It's a byproduct of other mining, and quickly being phased out for cheaper less controversial materials.

Lithium mining gets a bad rap not because it's particularly environmentally devastating, but because of political narratives that try to prevent technological change. Lithium is really a mundane material. You never hear people complaining about potash mining or other similar salt extraction, lithium is just targeted because of the industries that it upsets, which are in turn orders of magnitude more damaging.

Which isn't to say that we shouldn't make it as environmentally friendly as possible. I'm just saying that if you fill up a tank of gas, you have a hell of a lot more to answer for when it comes to environmental karma than if you fill an equivalent lithium battery.
Germany has weird history of energy politics. 20 years oil heating was bad one. Gas heating was the good one. Now gas heating is bad one and heat pump with renewables is good one. After 20 years heat pumps will be evil, because imported from China or another silly reason.

My recommendation for German government: make electricity cheap and nobody will think twice installing heat pumps or buying electric vehicles. Current price 0.3-0.5€/kWh depending on location what is insane.
Renewables do not solve the demand problem because the demand curve is not static. It is useless to have 100% of energy needs met when it is 200% during the day and 0% at night.
No experience, but the company’s hiring practices seem a scam to some extent. They pay little, usually fooling inexperienced people, like, as the commenter above said, that they are sending people to space, and stuff like that. Funny, you over work too.