skysight-inc/HackerNews huggingface dataset:
This was a single physical server running multiple VMs using local NVMe storage. It impacted a small fraction of customers.
Of course not. It’s a jobs program for middle managers.
I think you need more horsepower for plex, and that was probably your issue.
Er, what? Don't they sell beer and wine at the roadside in Europe? At gas stations and rest areas even?
how about overhead lines to charge while moving? lets be creative here
“newd” -> “news”, wasn’t aiming for a portmanteau of “nude” and “lewd”.
I agree, articles tend not to get read by those who need them most. A warning from the CLI and a banner on the app management page with a link to a detailed explanation would seem like a good approach.

edit: sibling post shows there is such a message on the CLI. The only other thing I can think of is an "Are you sure you want to do this?" prompt, but in the end you can't reach everybody.
Noone involved expects this to be in place on schedule. This is a matter of politics first, policy later, realization maybe eventually. I.e., have some nice dreams, give people money and tell them to build something useful, then see what happens.
Aren't those for profit infrastructure? IMHO they will put as many as needed for the region.

These legislations are not intended to design the infrastructure but to enforce minimal availability at places where there's no enough commercial reasons to build one. The idea is that regions not lucrative enough shouldn't be left behind because when left behind in infrastructure people start migrating to other places and make the problems even more severe.

So, the companies and and probably the countries will have to foot the bill for bringing the infrastructure to such places and the expenses for number of stalls is probably a rounding error in contrast to the expense of building the first one. We will end up having 1 stall where it's rarely needed and as many stalls needed at places where the demand is hight.
Or peppering every outdoor surface with solar panels. What a techno-noir nightmare that will be. Otherwise, electricity generation via natural gas/coal would mean you may as well just stick with ICE.
I've done waterfall and agile over 20 years and have yet to see a SCRUM like system deliver for either the business or the developers.

Agile (regardless of SCRUM, Sprints, LEAN, KANBAN etc) only works where the whole project breathes it from business client to support. The contract can't be fixed term, fixed price and fixed scope and be agile. The closer you get the client to the project, the higher the chance of success because only they truly know where to cut scope or what minimum viable release looks like. There should be no surprises, fast loops ("I don't love that feature but I can wait until next release, it's good enough for now") and financial realism.

How you then organise yourselves doesn't really matter. Right now I'm at a company that's multi-tenant kanban, we release when the code is ready. That could be every 2 days, it might be once every 3 weeks. The product manager, who is very close the customers, decides when to push what's been coded out. It gets merged and then into the test/UAT pipe. Releases are cheap, test has a lots of regression automation. I describe it to management as a river. Keep the tickets flowing like water. Get rocks out the river, make it wider with more people or faster with better tech/stack/devops/etc.

Everywhere I've worked that has had a strict SCRUM ended up being micro-waterfall where devs might story point 1 sprint but the management would plan out the next 5 to get to a release date, story points were converted into estimates, which were converted into deadlines, guesses became promises and scope could never be cut. Developers end up burning out and that vital domain knowledge is lost (the worst companies think devs are interchangeable). It was almost worse than waterfall because with waterfall the project managers got the blame, with SCRUM, it's the devs that carry the can. As one colleague said after a ridiculous meeting where our story point estimate was being compared with another team on another project in another country "it's just a stick to beat developers with". And he was right.

You mileage might vary! My experience only.
I’d be shocked it having it in a comment vs the article link makes a legal difference, and it seems like an odd ethical one.
Food transportation is NOT a big contributor to global warming. Bulk transportation, especially with ships is one of the most efficient ways of moving things around the globe.
https://ourworldindata.org/food-choice-vs-eating-local
I'm not sure the Sam Kinison approach scales. We need cheaper cleaner energy. Growing food locally just shuffles the variables around for marginal emissions benefit with massive hits to scalability.
To your points and the other commenter:

Perhaps doing "nothing" is not best. It may be wise to put restrictions on large, publicly available LLMs to minimize impact and for the practical purpose that it is the easy route for millions of people to use AI.

I think your points are valid.

I hope, though, that leaders and citizens are aware that trying to put a full lid on AI is like trying to outlaw math or censor information. It's like trying to wipe Wikipedia or ban encryption. Sure, you may try to take out a website or strongarm Apple/Meta into backdoors, but you can't stop two people from sending each other encrypted data.
The second generation Mirai's range is 647 km (402 mi) on the EPA test cycle.

The Hyundai Nexo gets 570–612 km (354–380 mi) EPA range: https://en.wikipedia.org/wiki/Hyundai_Nexo
India had a scorching summer and now heavy rains in many parts of the country. The government is just being prudent and ensuring sufficient local stock.
Washington's overtime law included a three-year phase-in, meant to ease the process. Last year, overtime pay kicked in after 55 hours a week. This year, the threshold is 48 hours, and next year it drops to 40.

Schreiber says already, he cannot afford to pay overtime. Instead, he's brought in additional workers to spread the hours around. It's allowed him to keep nearly all his workers to 48 hours a week, not more.

This reminds me of how some businesses will cap work hours so that their workers don't qualify as "full-time employees".

In my spherical-cow-in-a-vacuum fantasy land, I would attempt to mitigate this by making all such laws use continuous functions instead of thresholds. This would also resolve a lot of the confusion around income tax brackets.
Why have just one layer of protection when you can have multiple? https://www.comptia.org/blog/what-is-defense-in-depth

Mistakes happen in the most secure systems. The more layers of defense you have, the less likely a mistake causes an incident.
A password manager matching on window titles would be a security vulnerability without additional domain checking.
But again: is the CTO really not able to spot the expertise or is the expert so detached that he can’t translate between the worlds anymore? I find it much easier to believe that the CTO fully understands that he has an expert in front of him who knows what he is talking about but doesn’t see the relevance of the recommendation. My doctor might tell me that I should eat more vegetables and I’m fully convinced of the doctor’s expertise, but I might still not follow the advice
That's where you go wrong - you see the nuclear bombing of Japan as an isolated event. Place it into the context of several hundred thousand people dying every month as it was at the time, and it will look different.
So they use 77% of their available land to produce 37% of their protein and 18% of their calories. Imagine how much cheaper calories would be if the land dedicated to plants were simply doubled. Thus eliminating a huge amount of starvation.
I remember my 56k modem running at less than half the advertised speed, and having to pay by the minute for the privilege, and that the phone number originally being "local rate" shifting into "lo-call rate" as actual local calls became cheaper.

2 TB would have taken me nearly 16 years, and cost as much as a house.
> and probably lots of other stuff!

Yeah, lots of botched React integrations, misuse of Serviced Workers, nightmare security roles, just to name a few daily problems you will run into when choosing Dynamics 365!
Talkzy – A meeting summarizing tool for Spanish teams doing scrum
Hey all!
I am unveiling today Talkzy, a tool I've been working on for some months now. I run a team of developers on a software agency located in the Canary Islands, and I have had some trouble keeping up with all the updates (there are 10-15 projects running at the same time).

I used to have a person that would create a summary of the progress of each project for me, and put it out in a nice email.

I tried tools like spinach.io but none of them seems to work well in Spanish, so I decided to give it a shot and build out one.

It has been super fun and challenging to build out the system and I'm proud of how everything fits together. Even though now it's in a private beta, I would love to know your opinions and what would make you want to use a tool like this in your software company.

Cheers!
> Yu and his team have previously found that people with immune diseases are more vulnerable to Alzheimer’s later in life [2]"

Does this include autoimmune issues like developing allergies in life?

[2] Zhang, Y.-R. et al. Alzheimers Res. Ther. 14, 130 (2022).
It’s a great time to start a moving company! People will increasingly start migrating away from the equator for more livable temperatures.
In the UK in the early 90s we had to pay

1) The ISP a monthly charge

2) The ISP a per-minute charge (these were things like cix, compuserve, aol, etc)

3) the phone company a per-minute charge

Later we had ISPs that didn't have a per-minute charge (Demon and the like), so it was just the monthly charge and the per minute charge to the phone company. Even later than that ISPs which were just a per-minute charge to the phone company came along. In the late 90s I think the phone company per minute charge was about 4p/minute in the day, so for anyone in the UK that would be about 9p per minute today, or if you ran your modem full pelt, about 36p per Megabyte.

Towards the late 90s you could have a flat fee phone charge, then dsl and cable came along.
I hope we've learned by now that Putin often lies
Depending on your background, learning either will be beneficial in that you'll learn about a C-like memory model. My experience is that Go is way easier to get started with (both in terms of the language and the libraries). It has a certain concurrency model baked into the language (which in Rust is available in the standard library). It's kind of a lower-level Python. Also I'd say that if you're not familiiar with either language, Go programs are probably easier to read, which can make a difference if you're not working alone on a project.

Rust takes a bit more effort to initially get results, but once you get there, you work in a language that gives you expressive ways to create abstraction (this is a matter of taste maybe), generates generally faster code, and does not incur overhead by garbage collection. Also, there are ways to write asynchronous code in an elegant way.
The price is that you spend more time learning about structuring programs in a way that the compiler accepts. Once you are past that point, you'll be at least as productive as in Go.

I used to dabble with Go and like it, but once I had to write more code, I found it more tedious compared to Rust. But as I said, more readable to the uninitiated, that was one of the Go design goals.
When I say "AI" deadline, I refer to this: https://www.ycombinator.com/blog/early-interviews-for-ai-com...

Apologies for the mic volume being low and then the Spotify kicking in much loader. Fortunately, finishing the Quest also automatically stops the playlist :)
The refuel time is dependent on the pressure in the tank. There's an intermediate tank that's used to pressurize the hydrogen before it can be pumped into the car, and pressurizing this vessel can take a lot longer when the main tank is empty. I'd say that the refueling time is only as good as petrol in the best case scenario.
fwiw, you can write Terraform in JSON too. Not recommending it, but it's equivalent.
Maybe I don't understand the math but overtime is 1.5x wage. So to get around it farmers hire 2x workers at 1x wage? It seems that hiring more workers should be more expensive.
The author appears to have missed cyclic dependencies as a barrier to cold restarts. In large systems, you could have built critical component A with no dependencies, and later on component B is built that depends on A being up. "A" gets redesigned and now depends on "B" being up (which is fine since B is already up). The knowledge of how to build (the original) A from scratch withers as old-timers shuffle off the organization's payroll (or mortal coil), and suddenly, you have a system that's impossible to bootstrap from 0.
Agreed. It's an effective strong-man example in the context of western democracies, though.

At least if you include the word genocide. And are also careful to not explicitly point out that Native American relocation and Black Slavery were both genocides that included lots of rape [2]. And are not in a school board meeting [1]. Etc.

[1] https://www.foxnews.com/media/author-sex-slavery-book-graphi...
If it makes you feel any better your click -> see paywall -> leave likely counts as a bounce. But I agree, archive links should be default. My strategy is to just immediately pass any major news outlet article through an archive service because they legitimately do not deserve my money or my eyes.
Training Data Free-for-All – Japan's AI Data Laws
In the LLM space, "open source" is being used to mean "downloadable weights"
They don't specify what types of issues they had with FFI which makes me somewhat dubious of the outcome here. There are tools to help paper over the rough edges of calling code through FFI, at least with Rust. Maybe the reasoning is more to do with the Go side.
It's interesting that you bring up Dota because I find that it's a ready example of the vocab point failing. When you listen to pros talk, they misuse words and concepts all the time but it doesn't matter because the other pros listening get the 'feel' of what they're saying.

(I'm not a pro or anything, just high rank, but to use myself as an example) I try to make an effort to use the correct words when explaining things to friends. But even I find myself saying things like 'just look at the [lane] creeps' to explain what I want my laning partner to do and then I realise how unhelpful it is. Because when they see the creeps they don't understand what I see.
Yeah, and I genuinely want to like Rust and I pick it up a few times every year (and have done for the last decade), but each time I get burned by trying to do something that would be trivial (and safe!) in Go or C.

Most recently, I'm trying to build a non-allocating, minimally copying `Lines` iterator which reads from an internal `Reader` into an internal buffer and then yields slices of the internal buffer on each call to `next` (each slice represents a single line, and it's an error if a line exceeds the capacity of the internal buffer); however, as far as I can tell, this is unworkable without some unsafety because the signature is `fn next(self: &mut Lines<'a>) -> Result<&'a [u8]>` which doesn't work because Rust thinks the mutable reference to self must outlive 'a, and explicitly setting the mutable self reference to 'a violates the trait. If I forego the trait and just make a thing with a `next()` method, then I can't use it in a loop without triggering some multiple mutable borrows error (each loop iteration constitutes a mutable borrow and for some reason these borrows are considered to be concurrent). The only thing I can think to do is have a `scan()` method that finds the next newline and notes its location inside the `Lines` struct and a separate `line()` method that actually fetches the resulting slice from the buffer.

I don't run into this in C or Go, and for all of the difficulty of battling the borrow checker, I'm not getting any extra safety (in this case).
>We need to take immediate action to reduce our carbon footprint and prevent further damage to our planet.

Human hubris won't let that happen; seems like we'd still rather throw money at attempting to control nature[1].

[1]https://www.mercurynews.com/2023/07/13/it-will-cost-110-bill...
Are there any at all? I've seen zero marketed, while EVs are starting to become prevalent and my city has electric and hybrid buses.
Can someone else confirm the url works? It may require you to be signed into twitter to see it.
On the other hand mass famine and children starving to death, especially in the global south, is pretty shameful too.
I did not complain. I’m simply pointing out that people don’t make these types of platforms for free. Profit may not be the main driver, but it is a necessity if you don’t have tons of VC money.
Except you can't run FreeBSD in Kubernetes really. Or really anywhere besides in VMs in the Linux monoculture.
I’m feeling a bit like an accidental time traveler, because I can recall a conversation at a tech meetup that had to have been at least ten years ago where someone was struggling with unique UUIDs because they were bursting above 1000 UUIDs per millisecond and not happy with the available options.

How old is UUID7? I can’t get the internet to tell me.
but if the number of hours you need worked is constant than its cheaper to hire a new worker at 1x wage for that extra hour than the same worker at 1.5x
I've been side-stepping this whole conversation by using as little infrastructure as possible. I'd absolutely be digging into IAC abstractions if I had a circus on my hands and no say over why it had to be a circus.

Going into a "cloud native" stance and continuing to micromanage containers, VMs, databases, message buses, reverse proxies, etc. seems absolutely ridiculous to me. We're now using exactly 2 major cloud components per region: A Hyperscale SQL database, and a FaaS runner. Both on serverless & consumption-based plans. There are zero VMs or containers in our new architecture. We certainly use things like DNS, AAD, VNets, etc., but it is mostly incidentally created by way of the primary offerings, and we only ever have to create it 3 times and its done forever and ever - Dev cloud, Prod cloud, DR cloud. And yes - we are "mono cloud", because any notion of all of Azure/AWS/GCP going down globally and not also dragging the rest of the internet with it is fantasy to me (and our customers).

When you literally have one database to worry about for the entire universe, you stop thinking in terms of automation and start thinking in terms of strategic nuclear exchange. Granted, one big thing to screw up is a big liability, but only if you don't take extra precautions around process/procedure/backup/communication/etc.

The benefit of doing more with less also makes conversations around disaster recovery and compliance so much easier. Our DR strategy is async log replication of our 1 database. I really like the abstraction of putting 100% of the business into one place it magically showing up on the other side of the flood event.

How about this for a litmus test: If your proposed solution architecture is so complicated that you would be driven to IAC abstractions to manage it, perhaps we need to re-evaluate the expectations of the business relative to the technology.
Waste of money on a dead-end technology.
Almost all science is in English.
How did you approach testing this? Anything to watch out for when defining abstractions? I'm following Crossplane's abstraction model.
A Plague Tale: Innocence
I wish I could go back in time to when we were all having giant debates about adding official DRM support to the spec for web video, and I wish that I could take all of the people saying "this would never be expanded to HTML, nobody is talking about adding DRM to prevent Javascript/HTML manipulation" and I wish I could slap those people in the face. In Minecraft I mean.

And then have a constructive conversation about how wrong they were.
Putin can stop whenever he wants by not annexing Ukraine.
Its surprising that people spin that west is responsible for a war started by Russia. The article says "We can stop the war by the west stopping supply to Ukraine". This is literally the way Russia wins the war and annexes Ukraine.

Stop being an apologist for the aggressor
Zelle is crap. It was created by banks to skirt regulations which make them responsible for fraud. It exists to make things worse for their customers which is why they pushed people to use it so hard.
Careful they may reintroduce them...
> The bad news is that I'd be out of a job if I chose your service in this instance. 47 hours is two full days.

There was one physical server down. That's it.
They even brought it back.

I've had AWS delete more instances, including all local NVMe store data, than I can count on my hands. Just in the last year.

Those instances didn't experience 47 hours downtime, they experienced infinite downtime, gone forever.

I guess by your standard I'd be fired for using AWS too.

But no, in reality, AWS deletes or migrates your instances all the time due to host hardware failure, and it's fine because if you know what you're doing, you have multiple instances across multiple AZs.

The same is true of fly. Sometimes underlying hardware fails (exactly like on AWS), and when that happens, you have to either have other copies of your app, or accept downtime.

I'll also add that the downtime is only 47 hours for you if you don't have the ability to spin up a new copy on a separate fly host or AZ in the meanwhile.
I was curious after reading: can the @disable behavior be modified at runtime? For long running programs I find it helpful to be able to set a certain log level up front but have a way to update it without rebuilding or restarting the program. There may be other operations that can’t immediately be shut down and restarted so requiring a rebuild or restart to get debug logs is not an option in those cases.
Seems like unfettered trade with countries with low labor and environmental standards makes domestic production unprofitable. Surely we can only compete by limiting domestic labor and environmental protections. /s
I would have suggested ProtoBuf too.

That said, there was a comment in their post about not wanting to tightly couple the Go and Rust since they weren't sure they could accurately represent their structures in both langs.

I don't know anything about this turbo tool, but it seems relatively low-throughput, and they intend to migrate it all to Rust anyway, so it's probably not a big deal.

That said; I'd have done this with binary comms and not JSON, ProtoBuf or not.
Should I wear a KN95 mask on long flights? A scientist took your questions
https://archive.ph/Np39f
100 workers working 70 hours a week at 20/hour:

(100 x 40 x 20) + (100 x 30 x 30) = 170,000

200 workers working 35 hours a week at 20/hour:

200 x 35 x 20 = 140,000
> An EU directive is either directly binding law itself (like the GDPR) or a requirement on its member states to pass a certain matter into local laws

Nearly. A /directive/ is the requirement for each state to implement legislation and a /regulation/ is a directly binding law.
This is about motorways and there I haven't seen a decrease in the amount of filling station stops just because it starts charged. If anything, electric has had an increase in fills required so far due to range limitations and the desire to avoid filling completely (for both charge time and battery wear).
This made me curious about setting up a landline again at my house (cause those work even in blackouts) and there are still a few options

My favorite by far is basicISP:

https://www.basicisp.net/About/BasicServices.aspx

This is a time capsule of a website (and company for that matter!) that apparently is still actively maintained!