skysight-inc/HackerNews huggingface dataset:
Good point, but when I sign in I only see GPT-3. My understanding is UiO students and employees have free access to GPT-4 while the other institutions had to buy that as an extra service.
It might have been the original idea (though taken into account the time period and context, I suspect we're missing possible overfocus on deployment by AWS ASG and smallish set of services).

What grinds my gears is that over years I found it a thought limiting meme - it effectively swings a metaphor too hard into one direction, and some early responses under original article IMO present quite well the issue. It's not like people are stupid - but metaphors like this exist to make shortcuts for thinking and discussion, and for last few years I've seen that it short-circuits the discussion too hard, making people either stop thinking about certain interdependencies, or stopping noticing that there are still systems they treat like "pets", just named differently and in different scope, but now mentally pushing out how fragile they can be.
> Flight information is public information. It needs to be. It’s not optional

Similarly the location of your mobile phone is public information, for technical reasons it has to be. Just like aircraft, your phone constantly broadcasts identifying information for all the world to hear. Additionally, just about anyone anywhere in the world can query the phone network for information about which cell tower your phone is connected to.

I suspect many would not be very happy if there was a twitter account tracking the location of their cell phone.
IMHO, super users are annoyed by the humanized responses. I don't want to see the error almost teasing me after I tried to accomplish something. Feels condescending. Especially the ones that start with Oops, Oh No etc.
web pages and it does matter a lot. Among others, Woocommerce runs 23.43% of e-commerce.
I see, we have different understanding of the word optimism

to me it's positive outlook on things, the confidence things usually turn for the better where we work together to make it so.

that's neither blind optimism, "lala no problems here, this is fine meme".nor is it naive optimism "oh ya negligible issues in that corner no real issues Pu bear" but hard working realistic "this ain't be simple but we'll make it work"

I feel in good company with this general understanding, for example
https://en.wikipedia.org/wiki/Optimism

and that's why I have beef with the downspin of the article, which overgeneralized a single funding in a narrow context to a broad rejection of hope, when you think about it.
nature abhors a vacuum
Swedish tax payers are already all-in on “green steel”. But it seems we are betting on a different process, using hydrogen gas to strip the oxygen from the iron. Paradoxically, if this new electrolytic process works it’s probably a (financial) disaster for us…

EDIT: For clarity, based on comment below.
How so? What problems have IBM solved that dell can't figure out? In my experience sysadmin/SRE work is rarely about the reliability of the hardware and much more about machine management like predicting when you're running out of disk space etc.
A lot of us are using it actively. It's so lightweight now that it s free, and it s somewhat better than vanilla js.
I agree, Go’s simplicity is the best thing about it. I think the same thing about ranges, I think I end up typing the same number of characters - but spreading it over three lines makes it feel “longer” than a comprehension like “forEach(f)”. But then I write the range longhand, and it’s no big deal.

Speaking of initialisation though, I do wish Go had an idiomatic way to initialise struct fields to specific values. I don’t care about the lack of constructors; mostly, I just wish I could have bools initialise to true sometimes.
Don't Zen 2-4 all have fTPM?
Mainly this part is funny:

OP: In that regard, both books are good for techies to read because every now and then it's good to read something that drags you out of your comfort zone and futzes around in all kinds of obscure nooks and crannies before getting to the mother fucking point -- if indeed it ever does. Getting to the point can be important, but there is more to life (and literature).

Commentor: Philosophy at the end of the day is about arguing a point; it isn't about producing an aesthetic experience. (Even though this statement directly against original post, it's so obvious to author that he does not feel the need to explain, but goes on a tangent how bad the writing is)

Me: Hahah the whole point of op is that there is value in not always having a point, but meandering...

Response: It was a meandering and badly written mess with no point.

Me: ...

You: Leave it to the adults.

Me: ...

You: You're not making a point!!!

(Considering the nature of the first comment and assuming you didnt do it on purpose, you ending with blaming me I'm not making a point is poetic to be honest)
I don't think users should be mollycoddled either, because that would be patronising more advanced users. It's just a matter of not making them sound too terse and abrasive.

Better still, have a failure condition that is symbolic in some way, or enforces certain intuitive interaction via the UI, instead of pushing error messages in people's faces. A good example of this, typing the wrong password in the macOS login shakes the password field, rather than displaying "INCORRECT PASSWORD!". That sort of thing.
Just a comment from a smaller user who has moved away from netbox and realistically went back to spreadsheets. Please don't see it as a negative, netbox may purely just be the wrong product for us.

Some background on our usecase, tldr at the bottom. We effectively just need basic documentation.
Which port on which patchpanel does this drop go to?
Which network port is that connected to?
What vlan should be assigned to it?
Which router manages that vlan?
What network range is on that vlan if any?
What IP address should this device be assigned?

I've always found it just a bit difficult to setup things correctly, partly because everything feels slow. To put it into perspective, I was eventually running netbox on a VPS with 2 Genoa cores and 4 gigs of ram and even then some queries would be slow and page loads felt sluggish. Ping to the DC is sub 1ms on that. To need to provide that much horsepower for a DB with an interface just seemed like overkill to management.

Our usecase was great in earlier versions of netbox, the worst performance degradation came around when the graphql API got pushed and newer versions haven't improved it.

As I said, don't take it as a negative, netbox is a good product and to be fair I have never submitted an issue for this nor have I made an attempt to dig into the code to fix it (you can happily blame Django for that). Internally we see netbox as something we probably didn't put enough effort into doing correctly but at the same time the performance issues are a dealbreaker.
RPS got bought out about five years ago and all of the old guard left. The new RPS is about 70% run-of-the-mill reporting that you can see anywhere, 10% awful promos for hardware sales, and 20% starry-eyed young journalists trying to emulate what RPS used to be.

Despite all that it’s still the best single site for gaming criticism, sadly.
Tip about Dart : Don't use initState for stuff that doesn't directly concern UI (setting the hint of a text field, for example).

Most of my Flutter pages rely either on having very few things to do, or having a MyPageController object such that the parent creates a controller, initializes it however it likes and the child page's behavior is dependent on that controller. A typical example of this would be the parent being a page containing a list, and the user wanting to edit a list element. Create a controller, give it the element, and send the controller to a child page where the user does the editing. On return, the parent can look at the element or other variables/callbacks in the controller to decide what should change in the UI.

This also allows finely-controlled interactions between widgets without having to delete with InheritedWidget or the likes. Of course you should use a state management library with this, even though a lot of the time I don't.
I could be wrong but I read your post as saying "politics can't deal with progress in scientific insight into the observable universe, thus scientists better be careful what they say." That's medieval. We are better than that... or at least we used to be. Otherwise the sun would still rotate around the earth.
Whoa, we're making progress in leaps and bounds
I am an aging parent, although possibly not as old as yours.

Why would I want random advice on health that my son obtained from a tech forum?
I think the sorry helps the user to understand that something is wrong and it's not some normal part of a flow that they just don't understand.
We’re on .com until we finish the transition to our new domain. The name of the company is Neurotone.ai. Further, the contract email I provided is .com. Thanks for your interest!
lol react. Never seen a good react project. They all end up a mess.
Yeah it's excellent, but I am pretty sure OP was talking about something else:

https://sales.bigmachine.io/curious-moon
> you may have different ethical standards

Isn't this the exact opposite of zealotry? Zealotry is imposing your ethical standards on others.
This is only useful for USA residents
I am curious what do you mean by high tech?
It's really great to see these kind of articles! Of course, this is just scratching the surface. I think the most challenging bit about understanding GPUs is breaking through the marketing claims and trying to understand what is really going on in the background. How are the instructions scheduled, how does the execution actually look like and so on. And this is where information can be very difficult to come by. Nvidia documents the "front-end" of their GPUs very well, but the details are often shrouded in mystery. It's easier with AMD, since they publish the ISA, but it can be still difficult to map their marketing claims (like 2x compute on RDNA3) to the actual hardware reality. Interestingly enough, we know quite a lot about Apple GPUs, since their compute architecture is very streamlined compared to other vendors.
This is terrifying. A small sample of 100 or so. Like learning styles and hierarchy of needs. Rubbish science used to convict or set policy. As a psych grad, this stuff bugs me so very much. First year we learned stats.
Main takeaway from the article and the highly rated comments:

Don't use selfmanaged k8s.
As someone who works with actual blueprints, I'll tell you that even those don't guarantee what the actual asset looks like.
The article starts:

> It’s not certain when or where the first wheel was made.

Nope, fuck that, I'm out. What an awful start.
The “weight differentials” are like, a patch that can be applied to the original weights, right?
The thing is, the code analogy still holds up pretty well if you ask me.

The linked article tells us how this code is self-generating and self-modifying, how the interpreter of this code is more complex than you may expect from a 4-word language, how this code reads from external inputs when it runs. Well OK, sounds very reasonable to me. No one promised the code will be easy.

The problem with the code analogy at our current level of understanding is not that it's untrue and not that it's too simplistic, but on the contrary that it's too complex to be applied on practice. What we do now is akin to debugging running linux system by analyzing bit sequences in the kernel image. Surely it's all code and data, surely the bit sequences of the kernel image do determine the kernel behavior within the environment of hardware. This framework is correct but not powerful enough produce good results.
In what journal do you publish then?
I really wish it didn't need to be asked. Be polite, professional, respectful, succinct, and for the love of god don't try to be cute. Is that so hard?
The Morning Brew #3876
Do you know if the Javascript type annotations is progressing? I didn't hear anything after the initial proposal.
"Rules"? LOL! The interpretation of the rules vary so much that there are Christians who think Catholicism (and Unitarianism!) are not Christian faiths.

The repeal of Prohibition was not anti-Muslim, despite it re-legalizing alcohol.

Laws regulating the production of pork for human consumption are not anti-Muslim either.

The repeal of adultery laws was not anti-Christian, despite the Bible firmly prohibiting adultery.

The repeal of Sunday closing laws was not anti-Christian, despite another Biblical prohibition of working on the Sabbath. (And it isn't like Christians are 100% in agreement about when the Sabbath actually is.)

Laws allowing divorce are not anti-Christian, despite how some people interpret Jesus's statement in Matthew "what God has joined together, let no one separate" as meaning that a Christian marriage does not allow divorce.

Just like none of those are anti-Christian, a low allowing homosexual marriage is also not anti-Christian. Millions of Christians find no disagreement between the rules of Christianity and the legalization of homosexual marriage just like millions of divorced Christians find no disagreement between the rules of Christianity and their divorce.

If you think homosexual marriage is against God's will, don't marry someone of your sex. If you think it's against God's will to work on Sunday, don't do it. If you think it's against God's will to commit adultery, don't do it. If you think it's against God's will to wear clothing woven from two different kinds of thread, as stated in Leviticus, don't do it.
I know someone who will love this for Dutch.

You might also consider to add a translation option. For example to read a French text which will immediately be translated to English.
Ah, cheers for clearing that up :-)

I went through The Unbearable Whiteness of Indie article trying to guess your reference - B&S got the greatest wordcount IIRC.

Can't say I've heard of Dirty Projectors and their "use of attenuated 'afro' elements" - I'll chase it up, but often I prefer to see some back wash on the culture: https://www.youtube.com/watch?v=BOValSt7YOY https://youtu.be/tvY31eN3gtE?t=41
I like the idea of Dagger and have been following for a while, but it seems like its tailored to get people to use their Cloud product.
eg. Caching.

Is that not the case?
Except you can do this:

```css
.hide {
display: none important!;
}
```

```js
function hide(el) { el.classList.add('hide'); }
```
Depends where you live, some places have more consistent sun across the year. Regarding personal autonomy, I wouldn't treat it as this binary thing. If you're survivalist minded, solar is your only hope at any level of independence, even if it's not 24/7 autonomy.
You have degrowth. Because degrowth is frankly, a disgusting ideology.
Can a reductionist approach be good enough to control life independently? Or do we need to emulate the full process? I am not sure if the point of the article is to bash reductionism, but maybe push for full understanding. Kind of like Newton's law fits well within Genera Relativity. A first step.
Thanks for your feedback on the title of my article. English is not my first language, and in my native tongue, the distinction between “learnings” and “lessons” isn’t as pronounced in this type of context. I appreciate the nuanced perspective and will probably update my title . My main goal is to share the experiences we’ve gathered over the years, and I hope that the essence of our journey with Kubernetes shines through, regardless of the terminology.
NextDNS also, just set it up :)
Could this happen in other parts of the world like London or Lisbon?

What’s the point of working hard and playing by the rules…
I've spent a bunch of time playing around with Docker's API directly. BuildKit is notable because its API is completely undocumented AFAICT - certainly the API listed under https://docs.docker.com/engine/api/v1.44/#tag/Image/operatio... is just the API for a normal non-BuildKit build. If you want a BuildKit build, you have to use the Docker CLI.

I did some digging and wiresharking, and I'm pretty sure it's undocumented because the API is _insane_. It starts as HTTP/1 from the Docker client to the Docker engine, but a key BuildKit feature is that the engine pulls files & data from the client on-demand, which is hard in a normal REST API, so how does it do that? By renegotiating the connection to flip the direction after the client connects.

That means: the client sends an HTTP/1 request, the server offers to upgrade to HTTP/2 by in reverse, and then the server becomes an HTTP client and the client becomes an HTTP server, still on the same existing connection. All actual communication then happens as gRPC, but backwards.

Absolute madness, and very difficult to document or support in 3rd party SDKs (and so they haven't) but it's very clever. Some more context here: https://twitter.com/i/web/status/1423353288129396740
Just give me a clear and concise error message so I know where to look for a fix.
”Choosing the right programming language for your payment application is about business requirements, not your engineers' taste.”

Good luck finding all these COBOL programmers :D.
The US government has now paused approval for new LNG exports [1]. This was big news in Germany because their government is betting on US LNG to replace Russian gas imports and wants to expand natural gas use to complement renewables (peaker plants) and phase out coal.

[1] "Biden pauses LNG export approvals after pressure from climate activists"
Reuters, January 26, 2024
https://www.reuters.com/business/energy/biden-pauses-approva...
I don't see the point of using semver (or at least telling us about the same guarantees) and then not making use of it.

If there were 10 breaking chances we should be at 11.x now, not at 1.x with 20 environment variables.
See?

Your solution requires more dev time and skill - which makes it way more expensive. Basic economics.

The main requirement most devs and users have for an app - that it runs and works reliable. Not that it is the most efficient solution.
Honestly, no. An error message shouldn't apologize. A good error message has the following conditions:

* Concise. ("You need to enter a number in this field, not text" = Good, "we're very sorry but we can't understand it if you write your age in text" = Bad).

* Clearly telling the user what went wrong without relying on technical jargon. The line number where something went wrong doesn't need to be in an error message; it's not something the user can do much with - keep that in the crash dump. The DLL name you're missing probably should be if it's from a runtime.

* Providing a means on where to find a more detailed error message/who to call to fix it if the user can't fix it themselves, with the right information to supply that person. ("Please call your administrator for help and use code ERR_CRAPSHOOT (128)" is good, "We're very sorry" with a ton of warranty warnings and a way too vague error code that can indicate a ton of similar errors is bad.)

* Avoid the notion of just reporting everything to some backend endpoint and giving the users no indications of what went wrong; this is only frustrating to the user, no matter how many apologies you put in the message. It's an answer that amounts to "your message is very important to us, please hold the line".
I actually find these to be irritating if not kind of offensive. (Like the "we are experiencing larger than normal call volume" that literally always plays.) Who exactly is sorry here? The computer? It doesn't (yet?) have feelings. The engineers? They're not telepathic, they have no idea anything just happened to you, let alone feel sorry for it. It seems to be at best a random guess as to how some group of people is feeling, and at worst a lie.
Hey, had a similar idea, would be great to chat - can reach me at my username on google’s mail.
As this video shows, it's just an outer shell that's on wheels, not a building.

https://www.google.com/search?sca_esv=4117407177bffc2f&q=nyc...
Yet another student wrongly accused of using AI for writing
> you are so obviously projecting the upper class life you have lived. Typical shithead.

I've never had an upper class
life, quite the opposite. What's a shithead? You mean someone privileged like you are now?

> You know what feels amazing? Having no clue how to pay the rent and then you figure out a way to pay it.

LOL if it feels amazing why don't you donate most of what you got and go back to worrying about the rent? No?

You clearly have never struggled financially. I still have anxiety about making it to the end of the month even now that I don't need to worry about it. It absolutely sucks and makes all your life worse.

I've never heard anyone who's actually struggled spout the nonsense you have.
Have you tried either in an incognito/private browsing session? If it works there then it could point to needing a cache/cookie clear. If not then the issue may lie outside your box (try a vpn?)
Were you just trying to be cute? ;)
> Genes are only a part of how your body is formed

And blueprints are only a part of how a house is formed. Two different teams of workers can build very different houses from the same blueprint. So what you say here sounds just like a blueprint, I don't see why that is wrong.

Edit:

> Consider also that your neurons, your red blood cells, your muscle cells, your liver cells, your fat cells etc all have the exact same genes. And yet, they are vastly different between each other, and you'll never see a fat cell divide into a red blood cell and a neuron, even though they are "built of the same blueprints".

Yes, and us programmers tend to deploy the same code to many different servers and tell some of them to be databases, others be frontend etc. It is just simpler and more robust to share code and then then just flip a few settings on startup to change what the server is.

A single blueprint describing many things that are working together and you can build any of those things is very common.
> or even more controversially, make money from FOSS

I doubt Drew is against making money from FOSS. He actually runs a business (businesses?) around FOSS.

I don't think it's controversial to make money from FOSS anymore. FOSDEM just happened, many companies making money from FOSS were there, and they are liked. Some specific ways of making money might be less appreciated, but not the whole concept.

People are not silly, they know money helps develop (free) software and also many would love to be paid to work on free software.

> That feels like hypocrisy.

No, that feels like living in an imperfect world and trying to make it better. To improve something, you generally need to be part of it and its imperfections.
Never met an app that could actually feel sorry (maybe someday?).

This type of behaviour just feels artificial and inauthentic in most products.

If your making an error message effort I'd focus first on being clear, concise and actionable. Try to establish some expectations for the user so they know how and when things will be resolved, ensure you're monitoring and alerting is appropriate to hold yourself accountable to those expectations.

If you really need to apologize, a human should do it.
IE8 is a bit of a straw man. We've dropped IE entirely when testing unless there's significant (1%+) usage for particular clients, but even the NHS in the UK has dropped IE11.

Edit: https://caniuse.com/?search=classlist.toggle and click Usage Relative.
> Zealotry is imposing your ethical standards on others

It’s even more specific than that though isn’t it? A fanatical belief in a single cause to the exclusion of all else.