skysight-inc/HackerNews huggingface dataset:
Honestly I think they're both fairytales at this point.

Tesla is WAY further away from fully autonomous driving than they're letting on to their customers, probably because a lot of people would demand refunds on their FSD charges if they knew there was a good chance it wouldn't arrive before the car's end of life in the best case.

Volkswagen's plan here is just as ridiculous. Autonomous driving is economically impossible to make work on a pay-as-you-go model. Who's going to front the cost for all the tech required in the car to allow for automated driving? Volkswagen? the customer?

What if the customer doesn't want automated driving - they're not going to just give you an extra few tens of thousands of dollars for a feature they don't want and would still need to pay extra for anyway.

If VW eats the cost then they'll go out of business making crazy expensive cars that people won't pay to reimburse. (Are you going to pay $8 for every small run in the car anytime you need to go to the shop for something?)

Just copy Waymo and Uber in terms of model (i.e. robotaxi) if you're going to do automated driving. At least that way the cars are consistently in use and generating revenue to cover their eye-watering BOM cost.
Julia has builtin language support that kind of array handling, including broadcasting.
So you're saying I've still got a chance?
Similar local PA vein: scrapple. They're both vehicles for less desired parts of various unspecified animals. Scrapple has some strong, distinctive spices, and it's usually sliced and fried as a breakfast protein.
I avoid AWS like the plague because it's not small business friendly. It just seems foolish to me why any org that wasn't mid-sized or above would use it. There are plenty of cheaper vendors in the world! Tons of them! They can literally be 10x cheaper with more resources. Wild.

If you actually have to use AWS though because you have RFP requirements to meet, then I would ask whether or not you can halt instances using CloudWatch. I don't know the answer to that, but Amazon makes it seem like you can. Although their documentation seems to suggest you can only do it for idle instances.[1]

[1]: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitori...
In my experience yes. We ran into a Cypress bug that was bad enough that we just switched to Playwright and it works great.
Zoom flexes its dominance in the SaaS Cloud space
> But back around the 1700s, were most currencies pegged to precious metals?

From 1792 to 1853, the US Dollar was pegged to a fixed amount of both gold and silver. It seems reasonable to extrapolate backwards in time using that fixed standard, though the changing relative values of those metals might give you some problems.

(According to Wikipedia: https://en.wikipedia.org/wiki/Gold_standard#In_the_United_St... )
Perhaps... But perhaps not everybody was supposed to go walk up in the first place: https://twitter.com/SarahBelleLin/status/1370071520953835520
If you compare the results of having a government to chaos, they create a LOT of wealth.
Nobody you're iMessaging with has iCloud Backup turned off. Apple is still getting ~100% of the iMessages you send and receive.
There is a big difference between Java and C++ classes. In C++ classes are not present at runtime, but in Java they are present at runtime, are accessible via reflection API and can be loaded dynamically at runtime.
> (2) drives dying

Is that really a problem?

I'm still able to find 1TB new hard drives at my local microcenter for just $30. So its not really that expensive to set up a 4x drive RAID10 or RAID6 array.

4x 1TB in RAID10 or RAID6 == 2TB with redundancy for $120ish. Go up to 4TB drives ($100 each) and you'll get 8TB capacity for maybe $400ish.

Prices suck right now, even for hard drives. (I used to get 6TB hard drives for $150... but the 4TB point still seems reasonable).

> (1) no backups and cryptolockers

That seems to be easily solved by regular ZFS-snapshots.
Thanks! I’m glad to hear that.
> I had already started internal blog groups and was encouraging people to write.

Can you give some advice around that? Was it one blog in general, one per team, per person? What tool did you use for it? What else do you think is notable about it?
Yes! The only issue is that it takes a beefy GPU on a PC. Which I guess would happen on most games like this, but it still means it's unplayable for me.
If you also have a direct line to your users, you could try asking them how much they'd be willing to pay for either some new feature that's about to come out, or for the right to early-access. Get maybe 3–5 data points and you should have a pretty solid case to management (either to charge retroactively for existing features, to charge new users for existing features, or to charge all users for upcoming features).
Short answer to the lede: no, the industry cannot cope. Or rather, it will limp along with bloatware, bugs, and malware exactly the same way we see desktop OSes bloat, or the way we see routers and set-top boxes hacked to become botnets.

In my 40+ years in the industry I've yet to see code get SMALLER. With the exception of Linux kernel 1.0 in the 90's which was a step backwards into smaller, more compact code, code has always bloated.

Damn. I just want a car with as FEW knobs/buttons/levers as necessary. Literally: make it as simple as possible. Like an golf cart! Is anyone else out there with me? I feel like Walter from The Big Lebowski regarding this: has everyone just gone crazy?
I'm right here. I'm a human. You can e-mail me. I'm a person!
Exactly, it all seemingly depends on the arbitrary decisions about how we define our basket of goods.

For example is it generic "clothing" or an individual outfit of clothing. Individual pieces of clothing cost drastically more pre-industrial revolution. Because of that, people owned a lot less clothes. Therefore purchasing power increased by that metric.

However consumers responded to clothes becoming cheaper by expanding their wardrobes. The average person likely owned a lot more clothing by the time the 20th century rolled around. That could mean purchasing power was relatively similar if the metric was generic "clothes".

I'm not sure either approach is any more correct than the other.
I guess I have to explain. The reason it’s a definition of a bubble is due to compounding. If the economy is growing at 1 to 3% while equities are going up 7 to 10% a year they diverge slowly at first but the divergence is exponential. What ends up happening it takes far more debt to sustain this bubble. Interest have to keep doing down so the payments stay relatively the same but at some point rates can’t go lower or a shock causing the ability to pay goes away. Then the bubble pops causing a liquidity problem(2008, March 2020) causing a massive sale off of the most liquid assets. So far the governments of the world have been transferring the liabilities of the most toxic liabilities from banks, pension funds, etc to the Central banks. It is an asset swap and doesn’t inflate the money supply directly but what it does do is tell banks lend all you want if you blow yourself up we will bail you out. This further inflates the debt bubble since banks now believe the fed has backstopped their loans there by limiting downside risks. This money being created has to go some where so it goes into asset purchases. Then you have margin and loans based on the assets further inflating then bubble. This creates a feedback loop since the increase in the asset prices increases the amount of money available to borrow which is often used to buy other assets further increasing the price.
I don't think that's an accurate representation at all. Look through the proposals and see, for instance, that it goes beyond anything that Firefox is planning to do.

Dropping third party cookies is just one small piece of it.
Might be worth it for those who can't drive for one reason or another. Otherwise, no.
It's really impossible, or at least impractical, to factor in all the changes in money supply, baskets of goods, inflation, growth in societal wealth, etc. to do inflation comparisons across centuries.

Gold has always been internationally recognized money, at least until Bretton-Woods https://en.wikipedia.org/wiki/Bretton_Woods_system. But there has never been enough gold to provide sufficient liquidity in the economy, so silver has also been considered money. And of course the gold/silver ratio has fluctuated historically. The dollar is derived from the Spanish silver doubloon, which was money in the New World. Britain restricting circulation currency was one of the grievances of the American colonies leading up to the war for independence. A doubloon could be divided into eight pieces with a chisel, hence the terms two bits to refer to a quarter and pieces of eight from pirate stories.

Apparently in law one troy ounce is still the official U.S. dollar coin https://en.wikipedia.org/wiki/Dollar_coin_(United_States)#Am.... So I would say a better measure of dollar inflation is to smooth out the fluctuations in the gold/silver ratio and fluctuations in the silver/dollar price.
That's interesting to learn about the Linux APIs - not something I knew.

I'm still not sure about the GPL claims though. Imagine I write a Python script which is entirely my own - the only reference it has to a GPLd piece of software is an import statement and a few calls to some APIs.

The Google vs Oracle case made it clear that API usage (and even re-implementation) falls under fair use. The rest of that script is entirely written by me, and therefore I own its copyright. I could even develop the script entirely without running (or even having on my computer) any GPLd software at all - relying just on published documentation of APIs, the usage of which has been established to be fair use.

If I send you just the script. I'm not distributing a GPLd work. Maybe you could choose to run it on your computer, at which point it would resolve my "import x" statement as pointing to some GPLd software. It's only at that point that there's any linking. If you had a different PYTHONPATH setup, the same module might be a different, proprietary implementation, or a mock.

What basis does the copyright owner of the GPLd software have to come after me? I haven't accepted their license. The only person they could possibly have a case against is the end user of the script - who has violated the GPL by linking my non-free script with their GPL software. But if they're not themselves distributing the combined work, is there a case of copyright violation?
A lot of the ideas communicated resonate with me. The estimation process doesn't work well, and creates friction when things change that can interfere with the delivery of what's actually needed.

BUT...how do you also maintain some degree of accountability? If timelines can perpetually slip due to changing requirements and there's no objective mechanism for identifying this, then things might not get delivered at all. Surely some delays in the delivery process are due to inefficiencies or poor prioritization -- deadlines help identify this.

Now, to some extent the answer lies in hiring. The right blend of autonomy and individual motivation negate the productivity slip that might occur in an environment where it's easy to procrastinate. The right people in the right environment will self-police and police each other (in a healthy way).

I appreciate deadlines as a mechanism for forcing a discussion about tradeoffs. If there's some cost to delaying things then I'm more likely to think carefully about taking on the associated work. This usually leads to better decisions. I (usually) avoid spurious refactoring and overzealous testing, and scrap features that are less important.

So, rather than do away with deadlines entirely I think it's important to build up a culture that:

* Avoids punitive patterns -- rarely should folks be held unaccountable for adjustments in the timeline. Unless it's a clear pattern, it's not the fault of the person.

* Embraces (sometimes a lot of) discussion about deadline adjustments and the associated trade offs. There should be some friction to missing a delivery date, but not so much that it prevents us from doing the right thing.

This is of course hand wavy and really hard to get right.
Gary Kildall – The Man Who Could Have Been Bill Gates
Some companies are famous for explicitly dedicating 20 minutes at the beginning of the meeting for silent reading in order to address this.
Tesla scammed people into believing in FSD. I actually believed it for a second too. Yet here we are with Elon Musk as one of the richest con of all time.
That little line is so toxic and terrible.

If my boss came round and said, "This is adenozine, he's supposed to know what's going on," I'd be pissed. That's just dumping blame.
It uploads your usage data and identifiers (presumably username) without consent, and does so via IP, leaking your city-level location to the developers.

My information is coming directly from its app store privacy label.
Author here, thanks for sharing this. Let me know what you think.

I'm trying to connect the dots on research on expert advice and our fields 'thought-leaders'.

The connection is a bit tenuous but I think contingent advice can be shown to be better than non-contingent advice. I also think people are too confident in their opinions.
> Set panic_on_oom, job done.

So any buggy app (or just a `make -j`) can crash the system?

Yea no thanks
The notion that computing devices that aren't wide-open are "kill[ing] curiosity and creativity" in anything other than a very restricted sense is a limited world view, yes. That such devices being available as an option at all rankles people so and drives them to insult anyone who likes them as mindless consumers (very common in discussions like this, on this site) is downright parochial.
Google already knew this of course. There's been several papers over the years on uniquely identifying people using disparate sources. FLoC would be part of that.
Dog ejected from car during Sunday crash found on sheep farm, herding sheep
He holds a grudge against J, but not everyone does. I write research code in J and it's a very good little language. For instance, scripting is much easier in J. (Dyalog) APL is much more like an APL machine (in the sense of the LISP machine).
Heart inflammation cases higher in ages 16-24 after 2nd mRNA Covid-19 shot: CDC
There's no way to entirely avoid breaking compatibility. If you allow small API breakages then at least all of the team is aware of the possibility and designs their processes to handle backwards incompatible changes. If you design your processes assuming backwards compatibility then you'll run into the 1-in-1000 case where it's not possible and have to stop everything to handle the major update.
People do more of things that are cheap, do less of things that are expensive.

The point of the pipeline was to lower the cost of moving oil, which would have accordingly increased oil production.

The goal of environmentalists is to make oil production as expensive as possible. Increasing the costs of transportation is part of that.
The problem (with the teams I've worked with, at least), is that you have multiple tools for documentation and you generally get overwhelmed and stop even trying to search.

I'm working on https://www.sherdoc.co/ right now to help fix that issue.
I can’t speak to this particular solution, but the problem is, in fact, complicated for two interrelated reasons:

- Modern UNIXes usually can’t communicate, and modern applications usually can’t handle, out of memory conditions, because of overcommit, necessary due to pervasive use of fork(), which is ingenious and easy to use but lends itself poorly to resource accounting. Compare with Symbian, which was very awkward to program in, but was resilient enough to run the radio stack and user apps on the same processor.

- While the monolithic-kernel ideal is to put all caches and other discretionary memory consumers in the kernel, that is of course impossible to achieve. Everything on your system has buffers, caches, or un-garbage-collected memory it could afford to lose, but the system can’t communicate or cooperate with itself to actually make use of that. Cooperating resource usage of untrusted processes which have different ideas of how important things are is a hard and mostly unsolved problem.
It seems that 'hardware' is eating the car, too. I want to just buy a small, slow, simple EV for picking up groceries and other city errands, for $5k-$10k.

It seems like the only companies making that are the Chinese, and usually only selling them in China.

Heck, it doesn't even need an Infotainment system - just bluetooth for audio and calls, USB-A charger port and phone cradle.
Is there something here that hasn't been said before? From skimming it just looks like the usual list of complaints we've seen a thousand times
It’s crazy to me too. A few years ago, all the card networks told merchants that any in person merchant who does not use chip transactions will automatically lose chargebacks, so whatever in person merchants have not converted to chip are simply not willing to invest in updating their systems.
Go was designed to not cause widespread damage in the hands of a mediocre programmer. It prevents people from being too clever at the expense of more boilerplate and general busywork. This is the exact tradeoff that google wanted to make.
I'm many thousands of miles away from PA, and it's loading fine for me.
This problem is solved by learning the language of mathematics. The limits of our language are the limits of our world. When we learn the language of vectors obeying the 2-norm manipulated by unitary matrices and collapsing probabilistically according to the Born rule, we have learned how a single qbit works.
Interesting that developers are expected to do all this other ancillary work that is the remit of other professions.

How often do we expect the technical writers, marketing, sales, management, etc to also do their share of writing the code?

I too would like to do lots less work and have other professions help out and be available for the scapegoat game when it goes wrong. Documentation not up to par, blame developers. Marketing failed to achieve goals, ...
> What alternative do we have today that is as open to tinker and invent on as x86 hardware that is also widespread enough that it actually makes any difference at all?

x86 hardware.
> As a consumer, I only want insurance if I think they've assessed the value to be lower than what I'd pay out of pocket to 'self insure.'

I don’t think that’s entirely right — the main value add of insurance is to the rare, mind numbingly expensive events — ER visits, crashing into a RR, house burning down, etc. You’re paying to minimize tail risk, including risk you couldn’t possibly self-insure against in reasonable time (my payments to insurance is not going to reach the value of my home — the bet is whether my home will ever burn down).

Regardless, it’s still a conflict of interest in this case
I grew up in Lancaster (just south of Lebanon county) and still visit family there often. There are all sorts of country stores and meat shops in the small towns. Each small town also has its own local chocolate company with Hershey being the most famous of course. In my humble opinion the best chocolate in the world is Wilbur buds: https://www.wilburbuds.com/

Anyway, check it out and don't forget to purchase sweet Lebanon bologna meat sticks for your trip home.
So what, those third parties will then request that first-parties run a cookie proxy to generate and relay your unique ID, in order to get better payout rates?
Work and Life ≠ Perfect Halves
Ahh yes. Good spot. Thank you for the correction
I asked this same question to solarcity when I had my panels installed 5 years ago. The deal was they come out, take off the panels, store them, and come install them again for $500.
Looks like Rust is the "good" solution for all of these?
I still wouldn't trust the plus character to not fail or whatever one day. I manually expand each short URL I get using various webservices. I'm sure there's an extension for that. I would still just walk to the expander website and paste it in though.

You're right. Short URLs are Shite urls.
> "I like Go. I use it for a number of things (including this blog, at the time of writing). Go is useful. With that said, Go is not a good language. It's not bad; it's just not good."

The problem I have seen with many other programming languages is that as they try really hard to become a "good language" they eventually always become a "bad language" because of all the changes which they implemented in order to become "good".
Needs a "2014" note in the title.
You're right that they do have an interest, but I think it is wrong to go as far as if the expected value of the loss is more than the premium then one shouldn't buy insurance.

Consider a risk of losing $200 with probability 5% on an asset of $2000. The expected value of the loss is $10. So under your argument, if the insurance company charges over $10, it's worth it to self-insure. But what does self-insure actually mean? I assume it means keep $200 lying around. If you only keep $10 around then you won't have the money to actually fix the problem, and convert a loss of $200 (say, repair costs) to a loss of $2000. Under my values here it would take over 20 years' of premiums to build up what you would need to save to self-insure!

As a consumer, I pay a premium (literally) to get rid of the risk and cap my expenditures. So in my example, there is some price between $10 and $200 where the insurance company can profit and I still come out ahead because I can take $200-P and do something else with it.

Of course, you are still correct that within the $10 to $200 do have an interest in making you believe that the value of the insurance is on the higher end of the range than the lower.
Nuclear is superior no doubt, but it's asinine to dismiss solar power outright.
I've always been a bit confused that this wasn't what DevOps was supposed to mean from the start.

Devs should be producing easy-to-operate code and their oncall should therefore not be burdensome and there should be tight cycles to drive it to near zero.
Are there some specific terms in their legal bits that you're concerned about?

Quite a few, but to give an example from high on the list, it appears that a SaaS company would warrant that software sold through Paddle is always bug-free, accept unlimited liability via the related indemnification requirements if it isn't, and yet have no right participate in or even know about any relevant process if something goes wrong. That's a toxic combination and hardly looks like a healthy basis for a mutually beneficial business relationship.

Other concerns related to the considerable flexibility Paddle appear to give themselves in terms of how they represent, price and provide access to whatever is being sold, again apparently without necessarily requiring the consent or possibly even the knowledge of the underlying provider. We're unclear about how much this might be necessary because of merchant of record legal model, but it has little to do with what we'd actually want to use Paddle for or why we'd choose them over other services for collecting payments.

For context, this is a new business but run by a team who have collectively founded multiple others before. Several of us are very much over wasting time and effort on the mechanics of taking money from our customers and complying with whatever rules accompany that. Obviously fees charged by a payment service do matter, but a moderate difference there is still insignificant to us if the service we use can offer enough flexibility for our needs and easy integration, and otherwise takes on as much of the mechanical implementation and regulatory burden as we can shift.
Mighty morphin’ flat-packed pasta takes on 3D shapes as it cooks