skysight-inc/HackerNews huggingface dataset:
They're both exploiting the same principal. It's more efficient to generate thrust by accelerating a large amount of air a little than a little amount of a air a lot.

Figure of merit is the bypass ratio. Props are 50-100, fans are 3-10.

So big advantage of a turboprop is a much higher bypass ratio than fans. Downside is props can't spin as fast and so need a high speed gearbox to drive them. And props loose efficiency at high speeds.

I think for large fast aircraft turbofans are a win. For medium sized slower aircraft turboprops are a win.
Apple generally encourages employees to use their devices as they usually would to “dogfood”.
> I don't think that was the entire point. But who cares?

People who like language to have meaning?

> which presumably Fielding wasn't picturing

Fielding was describing an architectural style. Although there may have been an element of advocacy, at the end of the day whether you used it or not was not his concern.

> The implementation of REST as practiced by the industry is largely pragmatic.

In the same sense that the implementation of airships in Boeing’s 747 is largely pragmatic, except for the part where Boeing doesn’t misscall their plane an airship.

> The article appears to be arguing for REST purity.

Much like saying a serval is not a dog is arguing for dog purity, yes.
Not everyone spends their days chasing frameworks in SWE, and not everyone spends designing the next SoC breakthrough in EE.

EE and SWE are both very wide paths to travel along.
False and an unhelpful / irrelevant comment. Perhaps parent was trying to be funny but I found it confusing.
I love how our industry likes to use official sounding names like the "Richardson Maturity Model" and the "Liskov Substitution Principle", etc, as if these informal ideas are on the same level as general relativity and quantum electrodynamics. Thanks Uncle Bob and Martin Fowler for your important contributions to science.
It is not that an aspiring EE switches to become a lawyer. EE is often a special kind of software development. Switching to a "software" job often enough doesn't deeply mean a change of proffession. You are still an engineer (at least in the interesting software jobs).

And it is not about "hustling to make the most money the quickest way possible", if you switch to a company which pays a lot better for a similar job. And as a lot of those jobs are located in expensive places, an engineering salary doesn't easily pay for a nice house or any house at all.
Gordon Letwin's "Inside OS/2" book from 1988 is still a very accesible intro to operating system design. You can find it free on https://archive.org/details/InsideOS2_201802
Interesting, but the cat is out of the bag.

Now REST means JSON (or other data format) over HTTP with respect to the HTTP methods
I'm currently doing research on this topic and we internally settled on hawkBit and SWUpdate.
Both are OpenSource and Feature rich, however ment for the more classic bare metal linux usecase, which means you will need a custom yocto OS.
>The stuff about needing to know a lot more physics or arcane domain specific stuff isn't so true

ha ha wait until you find out about microwave engineering.
So in ~2140? Miners will still get TX fees after that.

We'll see, or not.
It's just, why are we calling it "Rest"?

Just call it adhoc RPC with JSON over HTTP.
Ego+Pride is a helluva drug.
So you know, Grana Padano isn't a kind of Parmigiano-Reggiano, it's a similar but different kind of cheese.

A quick Google shows that Trader joes markets it as "Grana Padano Parmesan" so I don't blame you for the confusion.

If you really enjoy it, I'd recommend trying to get your hands on DOP Parmigiano-Reggiano and Grana Padano and comparing the two to taste the difference.

IMO, Parmigiano-Reggiano is absolutely the best cheese to put on top of things, but I'm in Europe where it costs next to nothing, even DOP.
Driving generally works well offline, but biking, walking, and transit don’t. Some random features like search history or shared lists also seem to not work or work badly offline. Maybe you and the parent comment are using it differently?
I can't see a rhyme or reason to oppression math and the arbitrary groupings, it seems to constantly evolve with politics and blog output. Same as with lumping all "people of color" into the same category. Does an Indian brahmin descendant have the same struggles as a Cambodian immigrant? They're both "Asian", both "POCs", yet their average outcomes couldn't be any more different.
Follow the pay. Everyone I knew in EECS flipped to the CS route because software salaries are so damn high. Electronics became a low margin commodity business, software somehow hasn't. And somehow the software industry has enough revenue to warrant hiring at a rapid clip (VC capital?).

Unless software margins collapse or we end up with a dev glut, there's no way EE can bid labor up to match.
Ok, now I am curious :) let's try some typical problems from the Python package ecosystem:

- Can you resolve precompiled GPU dependencies with system managed CUDA driver versions?

- Are there packages that can convert PDF to PNG without system dependencies?

- Can you run a Qt GUI app on CI without needing to do any additional system setup?

With regards to cross compilation tools like burrito, that's neat! But Python is not a compiled language.
> its also a problem for the InfoSec tools… How do they distinguish between an unmanaged private device on a private network or a unmanaged device on a corporate network?

Trivially, from the simplistic (check IPs and router MACs / SSID in use) to the marginally more advanced (deploy an agent that is only reachable from the corporate network) to determine if the tool should even be running in the first place.
The story is repeated all over the internet but even reasonably thorough articles fail to bring medical clarity. It’s always “nine doctors agreed”, “x-rays showed terminal cancer”, etc. In 1976, when he was diagnosed its possible, though somewhat unlikely he had a chest CT since scanners were just becoming available then. More importantly, what no accounting of this history mentions is a biopsy. Without a tissue diagnosis and without sophisticated imaging the story is sketchy.
1. Krebs' source was anonymous and he has not confirmed it to be the party responsible.

2. Ubiquiti is currently suing Krebs for defamation, and the lawsuit is the source of the allegation that Krebs' source and the indicted person are one and the same.

3. Krebs' original article does report both sides of the issue, albeit with a scathing tone regarding UI's security disclosure practices.

4. Even if Krebs' source turned out to be the indicted individual, it is still ethical to avoid revealing the source. No one has been convicted.

5. It is generally not a smart move to apologize for an action that is at the center of an ongoing legal action, in any case.
Show HN: Consuma – Build the right features for your users
Figuring out what features users want is difficult.

Consuma analyzes tons of similar products and tells you what features users like, dislike and want.

Its free, give it a try and let us know what insights you get :)
my garage looks like yours. noice.
That doesn’t apply at all here?
Here are tips (specifically for blogging/article writing) that I learned while working at a blog company: https://maxrozen.com/blogging-lessons

I use them everywhere now, and bring in significantly more traffic as a result (writing more often also helps)
The Rust Performance Book (2020)
https://arstechnica.com/tech-policy/2022/03/ubiquiti-sues-jo...
> The only people who watch bot chess-competitions are AI enthusiasts, not chess fans

Actually that’s not entirely true. Grandmasters frequently study AI openings and use them to search for new ideas to bring against their opponents.

While I generally agree with your sentiments, I see more of a synergistic future, where humans take inspiration from computers (and consequently it gets fed back into the machine).
distribution is 10 x more important than production.

this should now be a well known rule of thumb in a free(ish) market economy under conditions of imperfect information. You need to build a distribution channel either before or in parallel with building 'the thing'
It starts at $1,449.00 for 1080p screen, 8GB RAM, 512GB SSD.

Why would the average user buy this over the M2 Air?

Average user = Not doing anything that requires Windows or Linux.

M2 Air has a better screen, faster CPU (plugged or unplugged), faster GPU, more battery life, fanless, runs cooler, better speakers, thinner, and it's cheaper.

Also, I think not having function keys is a mistake. Touch keys are just awful on a keyboard. In addition, if you want to do even light gaming, you'd want function keys.
Russia will force banks to add biometric identification to mobile applications
> It puzzles me when people say that small companies can’t retrain every day because they don’t have FAANG-style budgets. It costs a few dollars, at best, to retrain many xgboost or scikit-learn models. Most models are not large language models

So true. This is a pretty easy flag that someone hasn’t actually been down and dirty with trying to train any actual models and doesn’t know what they’re talking about
Nutanix Objects violates MinIO’s open source license
No, I don't subscribe to Netflix or watch their content. I just think it's not correct to say that it's a "recency bias" if someone complains that Netflix has bad content.
Why would an employer looking to fire you care about plausible deniability? Even if your setup worked technically, if the traffic traced back to you then you'd probably find yourself fired under these circumstances regardless.
"it's easier to be clever than kind"
The typical solution is "If you bought this from India, you can only use it in India. Pay full price if you plan to go to Brazil, etc."

Not foolproof, but at least a little inconvenient, especially if you have one of those cheap VPNs that toss you a random IP.
That's what REST has come to mean.
You could always use Freetube which is for Desktop but if its convenient this way then I'll also give it a try. Thanks.
That doesn't sound great but was this person actually doing anything to interfere with you other than existing in your presence?

Just curious, and I agree it's unprofessional. I can be quite judgemental, though.
The trust in media, in newspapers and television, is hitting an all time low
It's the first I've heard of it. What am I missing out on as a (fairly vanilla) vim user?
funnily enough, points 1, 3, and 4 are all core parts of the book : )
RSS feeds are in my eyes the best way to follow cross-platform content in a single place without worrying about privacy.

It allows you to follow your favorite artists / content creators on instagram (via bibliogram), twitter (via nitter), youtube (via invidious), tiktok (via proxitok) etc. without having an actual account to these services or using obscure apps. You can also follow your favorite news site, subscribe to ebay search terms (if your looking for one specific thing), hacker news, blog posts and much more all following one standard on one platform.
some good managers write well, done bad managers too, and sone good managers write poorly. Possibly there are some correlations, but I’m certainly not convinced
I was a senior at TJ in 2020/21. You’re wrong, even though your reasoning should be right.
Does Glassdoor require verified ID or something to sign up? Why don't people simply use a VPN and appropriate email to sign up and leave reviews?
i would rec HTDP, simply because DrRacket has some very cool tools for tracing recursive calls
You can buy an alcohol still from Home Depot for $200.
It's also getting a LOT harder to get a totally alter-ego email address that's not connected to you. They want a working phone number now. And hardly any of the "temp SMS" providers work for them - all blocked.

I figure at this point I will need to literally buy a burner phone with cash if I wanted to create some identity not connected to myself online.
CNC machines for under $5k? Where might we find some of these?
I don't know if you read the article.

REST is a post-hoc description of how the web worked (at the time it was made).

You had web pages with hyptertext content, and that included forms. The forms had fields with names and an "action" destination.

The client (the browser) knows nothing about the server or even its APIs. It just knows how to send an HTTP request with parameters. In the case of forms, those parameters were encoded in the body of a POST request. That's it.

There was no "client side code" that talked to the server.

The "client side" is literally just the browser. Talking to the server is done by the user clicking links and filling forms.

I don't think the article is particularly encouraing you to program this way in 2022. Just telling you that if you are not programming in this way, do not call what you are doing "REST", because it is not.
I love electronics and circuit building. I’ve been told that the compensation is shockingly poor compared to that of software engineers. This didn’t affect my college experience, as I was already well into my SE career when I finished my degree. As I recall though, the course load was harder and the opportunities fewer.

Incidentally, I had a friend who was an EE who went on to become a Patent attorney. He told me he did so because he didn’t want to spend the rest of his life maintaining a print server design.
https://sfstandard.com/education/selective-admissions-are-ba...
Email hn@news.ycombinator.com if you really want to know :p
I think that MLops somewhat subdues the modelling and research effort in commercial settings. At least anecdotally I only seem to see the coexistence of ML pipelines paired with the “feature engineering” + fit(X,y) approach to data “science”. What I don’t see is first principles research, leading to insight, leading to models to exploit insight which ofttimes requires heavily augmenting how and what data is collected: that part almost never fits neatly anywhere. In its place DS often starts with data then looks for models to fit it. MLops reinforce that pattern, and we end up with the old joke:

Man searching for his keys under a street lamp in the dark. Police man asks “Is this where you dropped your keys?”. Man says “No, but this is where the light is”.
All great points.

>We could, trivially, outright stop all anonymous trolling and disinformation. Purveyors of social media don't authenticate their users because they don't want to. Their business models require that they remain willfully ignorant.

Yes well what argument would you make, if you could or would, to change the current landscape?
* Every time you open a new tab, the new tab loses auth status and needs to re-auth. When I opened tabs for a bunch of VMs I got locked out for hitting the auth endpoints too quickly. Auth happens with a nonce so if you open two tabs, completing auth on the first tab causes the 2nd tab auth to fail so you need to refresh and do it again.

* The UI doesn't list any info on VMs, you have to click on each vm to see the details. Going back loses your list filters, etc.

* If boot logs get too large they never load in the web UI, you have to dig up the storage path, manually dig through the blob storage UI to locate the file, download it, and look at it with a local editor.

* Unlike AWS, they decided it would be better if every resource had a composite ID - subscription, resource group, name. You need to carry these things around together throughout your code. In the Go library you need to pass them to separate calls as separate params, for other things you need to pass them formatted as a URL path (generating the path by hand).

* The Azure official Go library shells out to the Python CLI to do saml auth!

* The Go library goes 100% against Go paradigms. API calls return a future, which then needs _2_ more calls to wait for and get the result from (WaitForCompletionRef, Result -- rather than just blocking the goroutine), each with errors that need to be checked. One of the two calls seems to be a leaky abstraction working around the fact that Go didn't have generics.

* WaitForCompletionRef never returns for a VM if it doesn't boot. So if you have a multi stage boot it'll just hang there.

* Their Go library is the epitome of inconsistency. There's at least a handful of different auth methods, and they have like three or four simultaneous generations of library apis (in the same library) that are all incomplete. To this day, constant breaking changes, dep incompatibilities (with their own libraries, with newer/recent older versions of Go). Iterating collections was similarly painful, with multiple "Paginator" object styles each with unique idioms (and dozens of bugs due to not getting the idioms quite right -> skipping pages or ending iteration early, etc).

Half of it feels like someone said "We need to be different from AWS so it doesn't look like we're copying them" but since AWS was doing things the best way they had to do things poorly instead.

(edit: AWS has tons of issues and I don't want to pretend otherwise, but the comparison to Azure is night and day)
>Edit: must be lunch time at MSFT. Downvote flurry.

>Please don't post insinuations about astroturfing, shilling, bots, brigading, foreign agents and the like. It degrades discussion and is usually mistaken. If you're worried about abuse, email hn@ycombinator.com and we'll look at the data.

>Please don't comment about the voting on comments. It never does any good, and it makes boring reading.

https://news.ycombinator.com/newsguidelines.html
I disagree about well-developed error codes. Examples:

* There is no useful distinction between different kindes of bad requests (syntactically wrong, structurally wrong, not applicable to the data found, etc.)

* Special handling is needed to test if a resource exists -- you cannot just GET it and check for a 404 code because browsers log all 404 as errors, even if it's the "happy path"

* The error codes confuse authentication and authorization

These error codes are useful when there are middle-men (e.g. proxies) that can understand them without having any application-level logic. But for most REST APIs you don't want those in the way, so that point is moot.

My (to be evaluated) opinion is that RPC is underrated because there have been horrible RPC monstrosities in the past, though I'm aware that without any well-done RPC this opinion is useless.
That would require the introduction of negative interest on cash and land value taxes including a citizen's dividend.
It took us a little less than a semester at Uni, so roughly ~2.5 months, if you are doing all the exercises? Note that this was 1/4 classes we were taking that semester, so probably less
HTTP is just a transport for your RPC. It's an implementation detail. At the HTTP layer, the transport was successful, so a 200 is appropriate.

A 404 would indicate 'not found' at the transport layer e.g. a bad proxy configuration or you didn't hit the right server at all. You definitely wouldn't confuse it with '${my_widget} not found'.
Bosch eBike Systems presents its new eBike ABS
They literally encouraged password sharing: https://twitter.com/netflix/status/840276073040371712
That gives you more freedom
Yikes, sounds like a manipulators fantasy.
A car? Google wikispeed
> It makes no sense. Why is web software so easy to make money in? Why do we value hard engineering so little?

Value is determined by quantitative exchange in a market and not by any intrinsic qualities such as difficulty of labor.
You can Martingale with finite money too.
Software has analogous constraints, with regards to scale, performance, latency, design, etc. Everyone thinks that a line of code can be quickly replaced. On a small program, this is true. But at scale, this is not true at all and anyone that's worked on a multi-million line application knows this. You cannot have every line of a complex system in your head at once. You cannot instantly solve for all of the interconnecting pieces in your mind at once. It takes a team of software engineers of various disciplines to consider the tradeoffs of any change to these complex systems. In particular when they are live and supporting millions to billions of users. And because software has more of an organic quality than traditional hardware, managing hundreds or thousands of changes that need to go into the system over the course of a month or quarter is non-trivial. People that think software is trivial are the same ones that fall for the idea that anything can be quickly refactored and redesigned and nothing will break and everything will go smoothly. It's just not true.

Most human beings can handle, at most, 5 to 9 variables in their head at once. Software systems grow to immense complexity of thousands to millions of variables, with various runtimes, databases, caching layers, frameworks, libraries, coding styles accrued over multiple decades in some cases, data aggregation pipelines, dozens to hundreds of APIs with their own unique interfaces, etc. It is a constant battle against entropy, which happens inevitably in such systems.

Meanwhile, there isn't a single modern "real engineer" who doesn't get their daily work done thanks to multiple software programs supporting their own productivity so much that they can replace what used to be teams of dozens to hundreds of assistants, techs, engineers, and other various human support systems. They draw lines on AutoCAD that automatically compute moments of inertia, shaft calcs, bill of materials, etc. Then they take that file output and zap it over Slack instantly to their colleague who works from home hundreds of miles away to get their feedback on it. Behind all of that is a team of software engineers and product devs that not only has to understand the constraints of their own technical systems, but the technical needs of their engineering clientele.
This is the way in. Garden tractor enthusiasts, VW camper van enshusiasts, vintage motorcycle enthusiasts -- they all want to customize, and will spend to get it.

A trivial electronic gadget to turn an oil cooler pump on and off is a good start. Electronic assembly isn't noisy or stinky. At most you might need to bend sheet metal for a case.

Guitar players love audio processing gadgets they can turn on and off with their toes. Make something that can be adjusted to give them a unique sound. Distortion is easy to layer on.
Another brilliant example of form over function.
The last psychatrist remarked [1] (I miss you), sadly, that women move there where men no longer are interested. With the fall of worth of [2] university education, the percentage of women increases.

[1] "when more women enter a field, it means less men did, and if the men stopped going there, where did they go? Why did they leave? I assume they aren't home with the kids, right?[...] if power seeking men aren't running for Senate, where did they go?" - https://thelastpsychiatrist.com/2013/01/no_self-respecting_w...

[2] "Ernst & Young will no longer require new hires to have a degree" https://medium.com/signals-of-change/ernst-young-will-no-lon...
It can protect whatever the contract says. Usually, severance packages include a nondisparagement clause. I highly recommend requesting that they amend it to say "mutual nondisparagement" and re-word the terms to apply to both the employer and employee. That way you get paid to shut up, but they are also forced to abstain from making potentially disparaging statements about you. It's a good ask.
There are three categories of theories relevant here:

Deterministic classical mechanics

Non deterministic interpretations of quantum mechanics (most popular among physicists)

Deterministic interpretations of quantum mechanics (eg Bohmian mechanics)

In the first case, the future is calculable in principle, but probably not in practise (too complex)

In both of the other two cases, it is incalculable in principle, even though the latter is deterministic