skysight-inc/HackerNews huggingface dataset:
I learned recently that Japan is often on 100V power so I'd think a lot of international components would support 100-240V.
You can't just say there's no cost because you don't see it. You don't have the option, so of course there's no way to tell price differentiation. I'm talking purely of raw material cost though. By adding a 3rd load conductor, you inherently add wiring cost and complexity, which should result in cost to the consumer.

It may be offset, as others point out, by power delivered being higher (and thus, wire gauge can go down) when running 3 phase... however that will largely depend on the load.
I've always been curious why Germany/France/European Union did not try to land lease acreage for solar farms and build the corresponding transmission lines.

To those concerned about sovereignty, costs and jobs, obviously that's not a concern because the alternative Germany pursued was Nord stream which is less sovereign and probably costs more (albeit the Russian oligarchs probably made the initial down payment) and the talent is Swedish.

Or lease space for factories in Spain/Portugal. Similarly, concerns about sovereignty, costs and jobs are moot because the alternative is to build the plants in Asia and ship the cars over.
I like that quote but JP Morgan may well have been projecting his own motivations onto others. You don't get to be JP Morgan without engaging in some amount of duplicity.

There is big money in whistleblowing, if your claim makes it through the gauntlet-- otherwise it's just a career-ending humiliation.

It's a lot of risk for a mother of three to assume; I'm sure she expected something (the DoD posters in the breakroom suggest as much) but I doubt she knew what the eventual payout would be from the start.
Oh! Wow - I'd never have guessed that. Thanks, and I agree with that point.
> Can [any storage that is not physically in my possession] be trusted with sensitive data?

No. You could make a case for E2E encrypted data where the storage provider does not have keys. That's pretty rare though. The point is, nobody gives a flip about your privacy. As soon as men with guns come asking for your data, any data business will hand it over without hesitation. Men with badges are only very slightly less threatening than men with guns, as everybody knows who the men with guns work for. So if you think anybody or any business is going to die on the hill of protecting your donkey porn collection, you're delusional.
Huh? Many content creators on YouTube have made TV shows over many episodes on YouTube, Wong Fu for one.
Most Americans drink substantially more coffee than tea, which is why we have a purpose built appliances for making coffee, and have had those for decades.

The reason Americans don't have a super fast boiling kettle is that very few Americans WANT a very fast boiling kettle for large portions of water. If an American wants a cup of tea, two minutes or less in the microwave is sufficient. I don't care if you think that's bad, because I want a cup of tea, not some elitist purity contest.
What prevents a virus maker from using Realm Management against virus/security scans?
I don't see how it's possible to show that the solution is lifted by the LLL as opposed to a arrived at by the LLM.

It seems to me that such solutions are soon to be within the set potentially constructed by an LLM.
Agreed but then who would manage the state clerks IT department? Deloitte? It’s a case of “You’re in the wrong but we secretly need you because we are even more incompetent”
Amazon CEO Andy Jassy’s brutal message to remote workers
I introduce to you https://aws.amazon.com/snowmobile/
> The underlying issue is the fear of change and the sunk cost fallacy of already written code. If you have the wrong abstraction, you can change it.

It's not that trivial. Consider that the wrong abstraction is reflected into your API (common), and consider that your API has many users. You are stuck with it, or you have to convince multiple teams (or, god forbid, external customers) to migrate to a better API. This can constitute a humongous waste of SWE-hours ($$$$$) and take quarters to accomplish, assuming you can get any buy in.

I think it comes down to what your organization looks like and how many users are going to be touching your code. If your abstraction is just for yourself internally and everyone else is not allowed to touch it, then fine. You will own the tech debt if the abstraction is wrong. If your abstraction has other users at your company, or external customers, it had better be the right one or at least an unavoidable stepping stone.

> If you created too much duplication, you can remove it.

This is actually true. Refactoring duplicated logic is a lot easier than fixing bad abstractions.
Codswallop. Corsets were not the restrictive garments our modern mythology would have you believe. Except for a few specific types of fashions, corsets throughout history were designed to be well-fitting and maneuverable. Women wore these garments while working - including lower class women working fields, factories, and other hard jobs. Corsets were effectively bras for these women, and you could absolutely bend down to get your own handkerchief. These myths have been well documented and debunked by the historical costuming community [0-3].

0 - https://youtu.be/zNwTqanp0Aw?si=3duaZETPo2IZwFqU

1 - https://youtu.be/rExJskBZcW0?si=sx1oClP0avxEMUUB

2 - https://youtu.be/Xpie2GL0M4I?si=HzP2g76ycNLiPCxB

3 - https://youtu.be/4XBLBfWNH7I?si=Kkr7t0y9bINlWsqw
Careful with your stones in glass houses, on HN, of all places. We're the community in which virtually every Web site we deploy sells out privacy of its users to third parties. And that's before we get into the commonplace UX behavior against users' interests, numerous startups which are essentially investment scams, some of our most celebrated startup successes only existing because an app is a smokescreen that lets them violate regulations long enough, and general background underhandedness and entitlement so pervasive that we now consider it normal.
That does read a bit like Neal Stephenson.
This is not true.

3. is supported by AMD on new hardware, e.g., Frontier.
See https://docs.olcf.ornl.gov/systems/frontier_user_guide.html#...
Now that you mention it I don't think I've ever heard of the thickness of non-stick coating being advertised in English language media.

Maybe it's a selling feature abroad?
HistoryNarrativeCheckerGPT maybe?
This latency is predictable by design though, no?
Correlation: A Misunderstood Concept in Finance
I don't quite know what a PhD-grade architecture would look like, but this seems like a reasonabke one to me.
Not saying it doesn't happen, but the situation in medical devices is more complicated.
There is a long history of intimidating people who dare speak out against corporations. Maybe not overt threats, but hard to know what is real when you are in the hot seat.

Are they just stalking you or are things going to get worse? If you are Jeffrey Wigand and some goons steal your computer, what do you do?
Optimize your physical health however necessary, which will springboard you into the next step: optimize your mental health, however necessary.
also Pascal is notorious for its single-pass source code parsing
Yes. Why not $10K per page?
Which is why we can't fix or even effect in any meaningful way by making McD offer lighter fare. What ends up happening is we end up paying a bunch of assholes with masters degrees to administer the program. McDonald's pays a bunch of assholes with bachelors degrees to figure out how to maximize their gain. Before long they are touting their healthful options which take up about 6sq inches on their board on commercials so that people don't feel bad or unhealthy when they roll up to the drive through window even though they actually ordered the double quarter pounder and the ass expander 2000 shake.

Fast forward a little bit and their lobbyists have convinced government to further incentivize healthy options by paying Restaurants that implement absolutely meaningless standards that do nothing for anything and we are actually subsidizing giant asses whose milkshake brings all the obesity adjacent diseases to the yard.

If you actually want to disincentivize negative things you have to either actually forbid them or just make it more expensive. Incentives will always be gamed and end up as free giveways. See bullshit carbon credits.

Want people to eat fewer big macs? Tax them at 100% and watch most of the cheap fast food implode and cease to exist. Want those people not to starve watch in amazement at a virtue of UBI you can tax things out of existence that destroy people's health without starving people.
> Not really. To do advanced stuff you have to understand the basics.

Doesn't that defeat the whole purpose of these abstractions? Can you read the machine code that your C compiler produces? How much of electrical engineering do you need to know to write a bash script? The physics of how a NAND gate is implemented?

It's obviously in the early stages, and I don't disagree with you completely today -- but this will just be one more layer on top of an already deep stack of abstractions that underlie all of computing.
The better monitors can be reconfigured to use the DCI-P3 primary colors instead of the default Rec. 709 primary colors (a.k.a. sRGB primaries).

(sRGB combines the Rec. 709 primaries with a certain nonlinear transfer function, while Display P3 combines the DCI-P3 primaries with the sRGB nonlinear transfer function and with the PAL/SECAM white, which is also used by Rec. 709 and sRGB).

With the DCI-P3 primaries, it is very noticeable that the red is much better, allowing the displaying of reddish colors that are simultaneously more saturated and brighter than what can be achieved with the Rec. 709 red.

While DCI-P3 also has a better green than Rec. 709, there the improvement is much less obvious than in the red area.
U.S. Announces First Drugs Picked for Medicare Price Negotiations
Sadly I think security systems will have to accommodate the possibility that someone else can see your screen. And hope that they can't see your keyboard.
Imagine if a race condition in someone’s backend was fixed by being slowed down just a little bit by this malware, and then the malware issue was surreptitiously fixed by the FBI and it broke again

https://xkcd.com/1172/
I wish you a longer life then. There is a lot to learn about security, and your conclusions are not among them.
I don't know. I come across old AP/routers where I've forgotten the login credentials and find myself hard resetting them with some regularly, one that's above "approximately never" anyway.
I just replaced one of my two HVAC units with a variable speed compressor. It cost a lot more than the single or 2 stage units but it is more comfortable, uses less electricity, and runs at "low" to dehumidify longer.
Who knows whether some things are inclusive or not? Who knows what use dates and timestamps? It seems like this should be abstracted somewhere and this knowledge codified in one single place. It sounds like your abstraction, in this case, isn't very abstract at all.

That is common for bad abstractions -- they add a layer but they don't actually encapsulate any knowledge. To use this abstraction, you shouldn't be passing any flags for inclusive/exclusive, etc -- it should know that for you.
It's also a kind of cult classic and there's strong evidence to suggest he knew what he was doing by making a horrible movie.
I enjoy this, though it's a bit hard since I don't know JS specifically. Definitely a nice game though!
mosh is quite smart with this
My point isn't that the single individual wire to your HVAC is $100 vs. a $20 cap, though. There is likely hundreds or thousands of dollars of additional infrastructure needed to handle 3-phase input to a house. You have breakers, busbars, the transformer into the house is different, and on and on.

I agree that less failure points is nice, however you have to consider the tradeoff. Is it worth $100? Probably. What about $1000? $2000? If it's $2000, why not just get a more efficient inverter based one, which doesn't have a starter cap in the first place?
Oldest Blockchain Companies
DietPi released a new version 8.21
DietPi is a lightweight Debian based Linux distribution for SBCs and server systems, with the option to install desktop environments, too. It ships as minimal image but allows to install complete and ready-to-use software stacks with a set of console based shell dialogs and scripts.

The source code is hosted on GitHub: https://github.com/MichaIng/DietPi
The main website can be found at: https://dietpi.com/
Wikipedia: https://de.wikipedia.org/wiki/DietPi

The project released the new version DietPi v8.21 on August 26th, 2023.

The highlights of this version are:

Orange Pi 5 Plus: New hardware support
Orange Pi 5, ROCK 5B, RK33xx SBCs: Improved hardware support, Kernel updates
DietPi HotSpot: Stability rework, support of WiFi6, WiFi5, also via dietpi.txt
Fixes and updates for DietPi-LetsEncrypt, TasmoAdmin, DietPi-Config

The full release notes can be found at: https://dietpi.com/docs/releases/v8_21/
Other providers are available: https://gitlab.com/
This whole article is based on a bad reading of the problem.

The problem that happens when code is first duplicated is that the correct abstraction is a fundamental UNKNOWN.

If you knew the right way to de-duplicate it, you would of course always construct that abstraction, because that would always be better.

What happens in practice is that the wrong abstraction is usually chosen.

Then that incorrect abstraction isn't usually held around because of "[feeling] honor-bound to retain the existing abstraction" (if that's a direct quote from Sandi then I disagree with the quote and feel it has entirely the wrong emphasis). The problem is that it is always easier to add a new knob to the bad abstraction than it is to go back and de-dup the whole code and fix the abstraction. So the bad abstraction tends to accrete more bad abstractions on top of it until it becomes a mess because of doing the cheap, easy thing.

We should not do that. But the realities of software development are that when you are dealing with an orthogonal problem, you WILL wind up adding a knob to something that can be done in a day, rather than taking 2 weeks to refactor a different subsystem that your original problem only barely touches and isn't the primary concern of whatever business objective you are trying to deliver.

So the advice is to let it sit for awhile. Let the code accrete a few more requirements over the weeks or months ahead, and when you find yourself doing a double edit to both sides of the code and the right abstraction is clear to you then go ahead and de-duplicate it.

Note that if the problem is TRIVIAL then go ahead and de-dup it right from the start. This isn't advice for junior programmers who are faced with something as simple as dropping two hash keys into an array and then iterating over it so that it makes it easy to add a third key. This is more about having two classes which are fairly similar and extracting a whole base class and jamming all the shared code into the base with a tightly-coupled poorly-thought-out "wide" interface (using inheritance as a hammer to de-dup code). And the whole problem becomes even worse if someone external might come along and pick up that base class and start using it with the existing API and you might be locking yourself into a shitty API that you can't change without breaking backwards compatibility.

And even if you're in a "non-OO" language like Go you can still make this mistake by designing bad interfaces, it is the exact same thing.
> Conscious duplication (often called “forking”) allows people who depend on a piece of code to change it without breaking anyone else.

Then that code is DRY by definition and simpler.

It can’t be Non-DRY because that would imply you’d need to change things in multiple places at once in order to avoid breakage.

If you have two separate parts that can evolve independently, without coordination then those parts don’t represent the same piece of knowledge.
You're right. It looks like they have had a few big rollouts in the last few months. Looks like a bunch of the EU countries are added now. I should have looked a little closer.

I tried it the other day and noticed it still isn't available where I live (Canada) for some reason...
The guy you are responding to was completely calm and reasonable. Didn't say anything attacking or otherwise. I'm not sure why you are seemingly trying to cast him (and the Beam) in such a bad light, with seemingly no reason to back it up.
Elixir has a repl too! and I mean a repl in the LISP sense of a REPL. I can open a repl on my machine and peer into a production machine and its internals.
> My understanding of the “duplication is cheaper than the wrong abstraction” idea, based on Sandi Metz’s post about it, is as follows. When a programmer refactors a piece of code to be less duplicative, that programmer replaces the duplicative code with a new, non-duplicative abstraction.

I think one of the main takeways from Sandi Metz's quote is that you should postpone creating the abstraction until after you have the duplicated code. Sometimes you will remove the duplication when you have just two implementations, sometimes you will want many more. Once you have the repeated code it's relatively easy to make the right abstraction.
Even stranger than that, Japan has two grids, one at 50Hz and one at 60Hz!
1. I said we will need new models, not that it wasn't possible

2. It's more of a total through out problem, even if OpenAI ran all the models, you still need the hardware capacity. We are already two years behind in supply vs demand vs manufacturing capacity. A lot of people cannot even try to build, this happened to me over the weekend

3. I'm not going to do research for you. Certainly doing simple searches is not enough to understand where things are going. You have to stay tuned in to the progress and have your finger on the pulse. There are plenty of prominent accounts on X to follow and be aware of what I'm pointing out here. You claims about what is to come are likely exaggerated because you are only understanding the surface at this point. Keep learning and researching!
Long Before Tesla, the Comuta Was America's Favorite EV
Speak for yourself. I would never leak or sell user data. I just develop B2B software that provides no value
And the big question is what if your machine is configure in a way that is incompatible with the FBI’s justice.exe and you lose irreplaceable data?
Learn a strongly-typed programming language (so the compiler can guide you on how to fix your mistakes), preferably with garbage collection (so the compiler can take care of memory management for you), preferably one that supports modern language constructs (so you can later on switch from one programming language to another without a lot of re-learning). The obvious choices are Golang, Rust, Typescript, Swift. I would probably recommend Golang, since it's the simplest and can be applied to various problem domains: command-line utilities, web development, etc. All you need to get started is YouTube online tutorials.
IBM develops a new 64-core mixed-signal in-memory computing chip
I completely agree.

But gaslighting people and pretending that overly grandiose claims/promises haven't been made in the past leaves a bitter taste, and doesn't inspire trust in core developers. Instead, it makes me think that the core devs are incapable of admitting a mistake - which would make their language a hazard.

For example, what if V gets huge and a serious security bug gets discovered - how can I trust that the developers will properly communicate the existence of such a bug and not just keep quiet about it, consider how they aren't even willing to admit that V has made some impossible claims/promises in the past? If I discover a bug, will they also pretend that the bug doesn't exist, even when confronted with indisputable evidence, because it threatens to damage their reputation?

As long as that attitude doesn't change, I'm not touching V with a 10 foot pole.
There is Fleet, which they purport to be their next gen IDE. Which I haven’t even tried, though I am am avid pycharm user, so maybe it’s not getting the results they hope for?
there's a joke that there reason there's so few jobs is 1) they are very high paying, and that the engineers are so productive they only need a few engineers to get work done.
Almost certainly some people were getting kickbacks for the work. With stuff like this it's rare there's not abundant personal incentives for those involved to continue the fraud.
Tell HN: Service Workers === Browser Background Tasks
The term "service worker" has confused me for a while, now I see it to be bad jargon selection. You can use "service workers" to send push notifications, load things from cache, and allow for offline behavior of your application (turn off your wifi and load twitter, for example). I think the term "browser background task" is more apt, I am sad another much more confusing and less relevant term was chosen years ago.
Readability. The most important thing for code is to be comprehensible by developers. Python has several factors contributing to readability. White space as syntax is the most obvious thing. More than that, unlike Perl which has more than one way to do things Python tends to have one or maybe two canonical ways of accomplishing common tasks. This makes it easier to navigate code without having much experience. Python was also good at interfacing with existing libraries from the start so a lot of work got scripted quickly in Python using high powered C libraries. Arguably being able to work with popular C interfaces was yet another factor contributing to generally high readability of code.
I'm not sure that's true, when I look at the code bases of some of the most productive coders I can think of (John Carmack and the Doom and Quake code bases for example), they tend to be fairly conservative with how much they abstract things. There's a lot of very thoughtful data structure usage (git is another good example of this) and diligence in maintaining a coding standard (which generally has little to do with formatting), but most of the code seems to be more concrete and task focused rather than abstract.

I think Casey Muratori has a good way of thinking about this, with his concept of "semantic compression" ( https://caseymuratori.com/blog_0015 ). To me that's a lot more valuable than the ideas that you get in say something like Clean Code (which in my opinion, the popularity of that book has been a disaster for the industry)
There are a lot of subsidiaries:

Walt Disney Pictures

Disneynature

Marvel Studios

Marvel Animation

Marvel Studios Animation

Lucasfilm

Industrial Light & Magic

Skywalker Sound

20th Century Studios

20th Century Family

Searchlight Pictures

Walt Disney Animation Studios

Pixar

20th Century Animation

Walt Disney Studios Motion Pictures

Buena Vista International

Star Distribution

Walt Disney Records

Hollywood Records

Disney Music Publishing

Disney Concerts

Buena Vista Records

RMI Recordings

Disney Theatrical Productions

Buena Vista Theatrical

Disney Theatrical Licensing

Disney Live Family Entertainment (DLFE)

Disney on Ice

Disney Live!

Walt Disney Special Events Group

Disney Studio Production Services

Walt Disney Studios

Golden Oak Ranch

The Prospect Studios

Disney Studios Australia

KABC7 Studio B

Disney Digital Studio Services
I think the issue described is when you're storing in a vendor backend, e.g. Data Dog or New Relic. If you're not careful with how much tracing data you ingest you can be looking at significant being 7 figures worth of bills.
I'm not in my seventies but I do have fond memories of the kettle whistling as a kid.
I always just called it the stove.
"The people we're regulating are really clever so we can't tell you what the rules are" Is a terrible way to handle things.
Hogfish can use their skin to ‘see’ what colour they are, say scientists