skysight-inc/HackerNews huggingface dataset:
But he is not lying, it is inaccessible for some people, myself included, I get the same error:

https://i.imgur.com/44KNIlg.jpg
I managed to get 0 mi, as well. I guessed the state based on the first image and was able to rapidly narrow it down from there. Kind of cool today's happened to be in the state I was born in, yet have no memories of.
Yep, I tried with double quotes, both times.
> cars are driven outside on the road, not at home

Are you just trolling now? :) Do you think people charge their BEVs in their living room?

1. Even solar is not free - hardware has a cost and finite lifetime. We're not close to post-scarcity with electricity, so there will be cost for foreseeable future. "Free" hydrogen from production peaks isn't enough for mass adoption, especially that grids start to use batteries too.

2. Even if a tanker beats UHVDC, I'd expect last mile distribution cost to be really bad for a physical good.

3. A wallbox costs $600+, which IMHO is already outrageous. I can't imagine electrolysis station with high pressure pump to be cheaper. 30 seconds plugging in a driveway beats 5 minutes refuelling.

4. Fuel cells are expensive. BEVs are already cheaper than hydrogen cars.

5. Reliability of hydrogen stations is currently pretty low, worse than uptime of DC chargers.

You imply there are going to be a breakthroughs in hydrogen storage and fuel cell efficiency that will make hydrogen cars not suck, but not account for possible improvements in batteries. They have been gradually improving over the last decade, and got an order of magnitude cheaper too. There are further improvements in the pipeline, especially that exponentially increasing demand funds further development. Physics of hydrogen storage however are as tough as ever.
Yeah, that's basically an actually good implementation of the pile of crap that I threw together several years ago while writing a few patches. :)

And yes, I linked to the spec files because there actually isn't that much test code written in Flow I feel; the high-level specs in the .txt files can be mixed and matched so much to create a lot of variety from some small number of primitives, so that's really where all the good stuff is. Implementation vs interface, and all that.
> Sure I didn't have to walk down the stairs to change the temperature a few times, but as the Thermostat started to bug out, I spent hours trying to fix it. I lost more time than I ever saved.

I've got an Ecobee, and I've never had a problem. The main reason was (unlike the Nest, at least at the time) it's fully functional in offline mode (schedules and everything). I've since learned that HVAC people typically dislike Nests, though I don't remember the reasons (and they are fine with Ecobees).

I'm not sure exactly what your problem with your Nest was, but they just didn't seem very reliable to me when I looked at them. Too much silicon valley in them: not prioritizing robustness, weird features that sound cool but just lead to an inscrutable device with a mind of its own, an over-reliance on the internet, etc.
A function should not have to be labelled as comptime to be run at comptime. There are cases when you might want to run the same function at comptime as at runtime (for example, if you want to do a thing with algorithm X but cache the result for a series of trivial cases as a lookup table).

Putting it at the callsite is more explicit actually and for example generating precompiled arrays clearly ties comptimeness to the actual artifact created instead of making it inferred from the signature of the function (which may be very far away in code)
SEEKING CO-FOUNDER | Software developer tool | CTO | SEA | Pre-Seed
Code-base explainer tool. Based in Singapore. MVP phase (www.birdlabs.ai).
Nah, that just makes that section of countertop "forbidden space". Can place anything on it (toaster, microwave, coffeemaker, etc.), can't use it for prep space unless you already know you won't need anything from the freezer. Can't let any dirty dishes pile up there.

But why not have a chest freezer underneath the countertop, but as a pull-out drawer? Same benefits of a top opening, but no need to dedicate a section of countertop for the lid to open.
> Food stamps are an injustice, however, the ends there justify the means

Thank you for so perfectly and succinctly illustrating my point for me.

You've apparently decided one "injustice" is okay and another one isn't, for reasons that are entirely arbitrary and based purely on your own personal value system.

But then, like the person I originally responded to, you dress it up like some kind of logical, philosophical argument, as though your personal opinion carries with it some kind of inherent truth.
The most interesting part of this to me is the UX feedback from the comments here.

Many people, myself included, say they had no idea at first that the photos were all meant to be from the same location, even though the very first sentence of the instructions was "There are five photos from the same place."

I'm pretty sure I read the instructions, I guess that just didn't register? An opportunity to reflect on how hard it can be to properly communicate with users, I guess.
Than you for your reply! I'm starting reconsidering the relevance of this idea after receiving some feedback here and on Reddit.

> Are you planning on building a public stats page?

I thought of having a "Hot" (per day/week/month) page.
Lowercase r written the American way confuses people in Poland. This is missing from the Wikipedia article.
I wasn't disputing that it's feed-forward. I just meant that stacked transformer layers can be thought of as an iterative refinement of the intermediate activations. Not the same as an autoregressive process that receives previous outputs as inputs, but far more expressive than a single transformer layer.
> Something went wrong. Try reloading.

Not 100% sure, but this might be related:
https://elixir-lang.org/blog/2023/06/22/type-system-updates-...
I got:

17 Mi -> 10 Mi -> 11 Mi -> 0.3 Mi -> 0 Mi!!!
>snippet of it needs the full license text attached, which is kind of bonkers if all you're doing is a citation

Eh, wouldn't that be fair use use anyway?
In my opinion the weirdness is that everyone is talking about how AI is so much better than humans and we're all going to get replaced. But almost nobody is talking about how tech companies will use this new technology to abdicate responsibility for the decisions they undertake. If you thought redlining was bad, you should see how mortgage companies treated people when they used an AI to accomplish the same goals. No thought was given to the effect of those decisions, only to the fact that this mysterious and "all-knowing" computer system told them it was a good decision. We're seeing the same thing with Facebook and "algorithms": "It's not us! It's the algorithm! We don't know why it does this." Which completely belies the fact that they wrote the algorithm and they should be held responsible for its effects.

We are about to enter a couple of decades of people using these pithy model systems to make real decisions that impact lots of people, and if I've learned anything in the past 20 years its that the impacts that technologists and "emininent minds" are predicting are nothing like what will actually happen. But terrible, banal things will be done at the behest of these systems and nobody is talking about it.
There is no AI risk. There is only the risk of bad or "unfavorable" actors using AI.

AI in a killer drone unleashed on civilians? The bad actor is the one who deployed this weapon.

AI given agency and goal maximization ending up gaining physical form all on its own and killing people? or hacking into bank accounts to enrich its creator?

The latter more likely than the former, but for cyber-offensive AI there is cyber-defensive AI.

Musk lately admitted that he's an AI accelerationist (following lots of the e/acc people and liking their posts) and despite his dystopian view of AI he's pushed it very hard at Tesla. He just wants the US to give him control of it (under the pretext that no one else can manage it safely.)
Let's address the last one, to make things bit more transparent

> My point still stands though, there isn't any specific item tying most of the people in this thread to CentOS that they couldn't pay RH or move to Debian/Ubuntu/FreeBSD. CentOS was never free from any of the items you noted above.

Hard to say on most people - I have gut feeling most of the population of HN is closer to development than operations and care on Docker/containers as platform, not the OS itself.

Agree on RH, Ubuntu. Don't agree on FreeBSD (due to reasons in previous replies) and largely don't agree on Debian. Debian has a short lifecycle and till recently required extra efforts on firmware blobs. I've superseded Debian to Ubuntu releases after Debian 8 or 9 for myself.

Point is on FreeBSD - it's total outnumbered hero in this list.

> now a 2 year release cycle is ok? but a (5) year supported FreeBSD release cycle is too short?

Right. 2 year (for Ubuntu, not for RHEL family) cadence doesn't automatically deprecate older releases - those still supported. So if you are running on 18.04 you can migrate to 22.04, no need to spend time migrating to 20.04.

For RHEL based, cadence is lower/more time between releases - RHEL 7 on 2014 and RHEL 8 on 2019, RHEL 9 on 2022. Real case, I observe right now, is future migration of Centos 7 systems to something RHEL9 based - Alma or Rocky - skipping RHEL8 base altogether.

> Not all companies release code to upstream repositories how do you think they systematically deploy their code from build tools like bamboo or jenkins?

That's more or less valid point for software out of your distribution's collection - like say Nginx modules which are not prepackaged or much more rarely - it's own software. Much more often home-made software is running in some sort of containers and packaged in Docker images, skipping "distribution" packaging phase.

> 3. Not even sure what you are talking about here. You don't have to run package updates everyday, you don't have to upgrade your FreeBSD OS everyday

I tend to run unattended-upgrades on Ubuntu everyday (by cron) and monitoring checking for security updates pending for more than 2 days, including "need-to-reboot" sign.
I'd expect something similar guys in FreeBSD land do (probably `pkg audit -q` or like that)
For what it's worth, I can't access it either, so there are probably many of us.
Except in reality, the cloud business would “buy” ads from the ad business, and now you have an “expense” despite the fact that the money never went anywhere.

Shuffle here, shuffle there, viola! Tax evasion.
Does Google's implementation of quantum computing help with this sort of scenario, or is it a really fancy way of breaking the bridge?
Holy hell this drove me crazy the other day. Firefox wouldn't work, but my backup, Chrome, did. But a fresh Firefox profile also worked.

So I figured I must've left a bad user-agent string or something in my about:config. But after lots of trial and error with FF settings, curl/dig, with VPN, without VPN... turns out it was because I was using Cloudflare DNS. I forgotten I'd switched a while back when I was getting dropped packets to quad9.

My best assessment is for whatever reason Cloudflare's DNS gives a different A record pointing to a non-TLS (or broken TLS) redirect, so Chrome worked because that's allowed by default. A fresh FF profile also worked because it defaults to DoH thus bypassing the problem completely. My VPN worked because it has its own DNS. But because my daily driver FF profile is set to use system DNS with forced TLS, it'd hit the broken redirect it got from Cloudflare and die.

So as usual, it was DNS.
There are very valid reasons for this. Historically, this is what happened.

* People did very basic qubit experiments with NMR in the late 90s. Very noisy experiments.

* Around 2000 they realized photonic quantum computers would be "easiest" because light experiences very little noise. The problem was that its insanely difficult to do non-linear interactions between photons (which is necessary to do any sort of non-trivial classical or quantum computing with photons). In 2001, somebody came up with a clever way of doing non-linear interactions by using fast detectors.

* Huge efforts started to try and build photonic quantum computers. Unfortunately, around 2004-05, people started to do estimates and it turned out that the number of sources and detectors needed with the clever way was humongous. Far more than we could hope to achieve, and there didn't seem to be any way of reducing it. People abandoned photonic quantum computing and started doing ion traps and superconducting.

* Interestingly around the same time in 2005, there emerged an alternate method of building photonic quantum computers, based on "cluster states". However, the method also had the same humongous resource problem, but it had an advantage: the framework could be modified and played with to improve it. Over the next two decades, very slowly people figured out improvement after improvement to this architecture to bring down the resource costs.

* At this point, this cluster-state photonic architecture has improved quite a bit and is starting to become very competitive with ion traps and superconducting qubits. PsiQuantum (whose article I shared above) is the leader in this right now. And they might win the race.
I’m in Canada where we’re (almost all) on the same interconnections as US. Texas (and maybe Quebec) are the bigger outliers when it comes to outlier systems.

https://en.m.wikipedia.org/wiki/North_American_Electric_Reli...

https://en.m.wikipedia.org/wiki/North_American_power_transmi...
Depends on in what form he's making use of them... most small holders end up leasing them to a bigger operator for a set period of time, with a cut to the agent who made the deal happen. Those leases have gotten a lot more lucrative over the past 20 years or so than they were in the 90s.

Texas will get state-funded universal healthcare and Tesla will be able to sell you a car right there in downtown Dallas before mineral rights are seriously reformed. For non-Texans: those first two things have two of the more powerful lobbies in Texas against them, but not the even more widely-distributed power of mineral rights holders.
I/O is something that literally every program has to do. Its also the bottleneck of 99% of code running on modern hardware. Moving bytes from one place to another is essential and relatively slow.

Understanding how to deal with memory I/O and file I/O performantly is a relevant skill for every program and programmer.
TERRA (YC W21) | LONDON | Full-Time/On-Site |

Terra is an API for apps to connect to wearables and sensors. We are Backed by YC, General Catalyst, and many more

Positions: | AI Engineer | Software Engineer | Growth Engineer | Product Engineer
Show HN: Using C++23 <stacktrace> to get proper crash logs in C++ programs
> Most individual gaming is done on smartphones

Perhaps, but only because most gaming in general is done on smartphones.

I reckon about 80-90% of the games I own on PlayStation are either single-player or online multiplayer, which is the same as single-player in what relates to the matter at hand.

PC gaming is even less social.
Same, XP was replaced with Ubuntu and support call rate went from "at least one per week" to "once per year"
Your definition of accessible reminds me of Cave Johnson.

"Bean counters said I couldn't fire a man for being in a wheelchair. Did it anyway. Ramps are expensive."
Pre-Order Flying Car
> it's Rube Goldberg machines all the way down

On another context, you have some processed data on the backend, and an infinitely customizable software system on the frontend... How do you keep them both in sync?

And yeah, it is by converting your data into a programing language; parsing it again; resolving incompatibilities; turning it into the presentation language; letting the user interact with the presentation representation; converting it back into the programing language; sending it back into the backend... But then you don't want a round trip on every single interaction, so you convert your backend code into the frontend language, so it deals directly with the presentation code... and it goes on.

Oh, on the backend side you have an application and a data layer, both using different languages and data representation; so you do all that dance again there... Oh, and now we want several independent layers between those too, so be prepared to do all of that again and again.

At some point we decided on the wrong abstractions for our mainstream architectures.
A co-worker drove to SLC from LA (abut 700 miles) in their Model 3 a few months ago. It took over 24 hours, including charging along the way, and they had to pre-plan their stops to make sure they could make each charger without their battery dying.

I recently drove to a campground in Yellowstone from LA (about 1000 miles) in an ICE SUV in less than 15 hours, including multiple rest/food breaks and traffic delays in the park due to road work. We didn't plan any stops on the way, and only got gas when we stopped for restroom breaks.

Right now, driving an EV means giving up a significant amount of freedom and turns what should be a pleasant road trip into a stress-inducing chore...and that doesn't even take into account the lack of charging options at home for those of us who don't live in single-family dwellings.
Location: Georgia, United States
Remote: Yes, only remote
Willing to relocate: No
Technologies: JavaScript, TypeScript, React, Angular, Node
Résumé/CV: https://docs.google.com/document/d/1-XjsbjMxUb7B58lVqfddBzahwZJ6o1pk5RSBiUu7AoM/edit?usp=sharing
Email: apozem@icloud.com

Experienced frontend expert with large knowledge of JavaScript and the frontend. Hoping to become more full stack with a chance to work on the backend.
"Something went wrong. Try reloading."

> Y'all's hatred of Musk is driving you to lie.

My god, my hatred for Musk has caused twitter to go down. Wow, I didn't know I had such power. JFC.
The thing is that the specific technologies behind all of those very practical improvements are not what's being hyped up this bubble. Speech recognition, for example, usually involves a lot of audio preprocessing, followed by some form of RNN/LSTM/Transformer to generate candidates, followed by beam search to score and choose from candidates.

If you are a machine-learning practitioner, you should be familiar with all of those techniques and how they are used so that you can solve practical problems with them. But if you just read about AI in the news and figure you're going to found the next great startup and make a billion off it, you'll probably start by feeding a whole bunch of data into Tensorflow and then getting useless garbage out of it.

This hype bubble is specifically about LLMs, extremely large-parameter transformers that are trained on all the data OpenAI or Google can get their hands on. And then supposedly if you ask them the right questions, you will get useful answers back. For people that put in the time and experimentation to actually find the right questions and the right applications, that will probably be true - but the hype is that this will change everything, and it most certainly will not, just in the same way that beam search is frequently useful but it definitely does not change everything.

But slick promoters will nevertheless manage to use people's lack of knowledge to redirect billions of dollars in capital into their and their employees' pockets, the same way that slick promoters used crypto to redirect billions of dollars in capital into their and their employees' pockets.
That's the expedient field repair, but what happens to the motherboard afterword?

They're under no obligation to replace your motherboard with a "new" one, so it's possible that it goes back to the repair depot for actual diagnostics and repair by better trained and equipped technicians.

I have no idea, maybe they do just shred it and melt it down, but it sure doesn't seem efficient for Apple to simply toss the motherboard rather than try to repair it themselves, otherwise the repair would be vastly more expensive -- AppleCare or not.
It's not waste.. it's cost.
IMHO, it's simply that predicting the future is difficult, and people disagree on what matters.
Every waymo ride I have had has been at least as good of a driver as a mediocre Uber driver.

Haven't tried it, but I hear Cruise is considerably worse.

> Have you ever seen one try to deal with a contested left turn, or a 4 way stop with pedestrians constantly crossing?

I've done considerable mileage in Waymo and these two situations it handles pretty well. I think the software is improving rapidly - I've reported some problems that happened consistently that a week later seem to have been resolved
I'm afraid consumers have grown leery of this kind of thing, though, between power companies messing with our cloud-enabled thermostats and appliance manufacturers harvesting data and good lord, nagging us with ads and popups and incessant updates on our damn fridges and laundry machines... not to mention transmission providers neglecting the whole scheme to death.

I've had a string of in-home energy monitors, and I've turned on all the relevent features for this, but at this point, I have disconnected everything from the internet to stop it being enshittified, and my local incumbent energy transmission provider has left all the consumer-facing smart meter services rot on the vine while the state of Texas kneecaps all the legislation that made it possible in the first place.

In short, all the industry and government entities involved have given up on the consumer here and have pissed it all away, and it's a shame.
It's just process & corruption.
I asked a MS friend because that looked suspicious. The post was seen by 220k people but it had only 5k emoji / reaction things (3k thumbs up and 2k hearts).

They did mention the post has an uncharacteristic number of negative comments, spread among the more usual ass-kissing variety.
Around me the plaids drive way under the speed limit everywhere and it's unsafe to pass them because of their ridiculous acceleration capability.
I agree. I read most of this as an internally facing focus. I feel like now days we are so cynical. You can't take pride in your work, or want to do a good job because you'll just be "doing it for corporate profit". To me, it's more internally focused, learning and building for your own benefit, because you want to know more or do it a bit better. I think the big thing is that you're not competing against anyone else; rather, you're just trying to do and be a bit better than who you were.
I think you’re extrapolating from yourself and you think you could learn any field given enough time. What about the type of person with a fixed mindset who thinks they aren’t good at math or chemistry, if ai can’t train them for whatever reason, even if the reason is the person is stubborn and/or willfully ignorant, are they more like a cockroach than a person?

What if someone tries really hard for a long time and can’t learn a field? Do they fail the intelligence test, or does their teacher?