skysight-inc/HackerNews huggingface dataset:
Semiotic breakdown:

Ok, jumping into the deep end of the pool, potential semiotic [0] interpretations:

bug screen (Poisson) & computing grid (Fourier).

Permits one to crunch the numbers without eating the sprinkles. aka gets around the 'You can't have your cake and eat it'[1] issues.

symbolically supports the no formalism approach: a) Pi is irrational number. b)Raspberry is stand in for Bronx cheer [2][3].

Perhaps not being able to eat the cake & complete the project is a good idea (less sugar high & more realistic interpretations/results).

[0] : https://www.uvm.edu/~tstreete/semiotics_and_ads/terminology....

[1] : https://en.wikipedia.org/wiki/You_can%27t_have_your_cake_and...

[2] : https://www.collinsdictionary.com/us/dictionary/english/bron...

[3] : https://www.urbandictionary.com/define.php?term=Bronx%20Chee...
I am a community member of the Gitea TOC, and there will be no open core model.

Gitea will remain fully open source with no tiers.

The community TOC also has advantages in any such voting where something may negatively affect the OS project, although as you mentioned that hasn't happened yet, and I don't expect it will.
If you know who to follow. It's still much to be done with account recommendations
Yeah—being able to play pirated Gameboy games on my iPhone and turn my iPad Pro (or, even better, Apple TV) into the heart of a console emulation station is about the only thing that'd change about my use of iOS if sideloading were opened up to a free-for-all rather than the annoying time-limited thing they do now. Might also pirate discontinued iOS games. It'd 100% be piracy-related, for sure, all the non-piracy stuff I want to do, I already can.
Your complaint seems mostly to be about the tone of the people who are angry at you.

Again, I invite you to consider if that anger occurs in a context that might make it be or seem justified.

For example, many people are a little irate when they are on the cusp of losing nearly everything.

Many people now perceive they are on the cusp of losing everything. Are they, really? I'd say, yeah, probably.

Either way, your feelings about people who are angry at you are not as important as understanding those feelings, and understanding the feelings of the people who are angry at you.

Go for the understanding. "I'm fatigued by the anger" is not an appropriate response to a circumstance where your team may in fact have done something very wrong.

Are we the baddies? https://youtu.be/hn1VxaMEjRU
In theory, these are all just loans and they get paid back. In practice, the Fed's balance sheet just keeps increasing. A loan that always gets covered by a bigger loan is never really repaid, and a loan that is never repaid isn't a loan, it's a payment. These are payments disguised as loans. A fig leaf over a money printer.

Look, I understand that you don't want to base your opinion on speculation about the trajectory of the Fed's balance sheet, but do you see how this refusal would give the Fed license to print money in exactly the manner I describe, by perpetually growing the balance sheet?

Let's be concrete: would you be willing to bet me $10k that in 10 years the Fed's balance sheet is under $10T? If not, I rest my case: this is money printing, not liquidity provision, and the smart part of you not willing to take my bet understands this.
This place is amazing for hosting events. They have a side room that’s perfect for a birthday party.
Cloud computing is a massive rip off. From my experience with start ups, they were using things like AWS, because otherwise the investors would be reluctant to put their money in. As in they were afraid of dedicated hosting and something that small business wouldn't be able to handle.

So for instance company would have their hosting costs upped from £500 a month (dedicated servers) to something like £5000, so that they could "scale up", while their dedicated servers could have easily served almost any traffic thrown at them and be more responsive. They have actually never reached the level of traffic that this old set up wouldn't be able to handle, but investors were always saying "what if we get sudden surge of users" which has never materialised. But then it was their money so nobody objected.

I can see that now that hosting costs in the cloud have become ridiculous, cash strapped smaller businesses will be looking for savings and the cloud is quite an obvious area to look for cuts.
> What would you do if all of your favorite sites switched to subscription models?

I have very few truly "favorite sites". Most of them are completely disposable. Eg, I don't see myself ever paying for a website that provides song lyrics -- it's a fully optional service, and entirely fungible.

I think it's possible a limited return to an "old internet" model to some extent, where some random person might just posts lyrics of their favorite band just because they like it.

For the very few actual favorites, probably.

> Would that be a win in your book? Always honestly intrigued by such world views.

Extremely so. First, no ads. Second, a site that must please its users or go bankrupt. That's a win/win in my book.

Such a change likely comes along with improvements in the site's quality. Eg, paid Youtube competitors don't want to feed me hogwash all day in hopes I watch more ads. Bandwidth is expensive, they're not getting any more money from me, and there are no ads to pay for increased consumption. So their priority becomes a smaller amount of high quality content.
Apple has John Giannandrea who was previously in charge of Search and AI at Google.

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

Apple has a tendency to keep things close to the vest, but I am sure they have a plan. If you look at the M1 and M2, they have insane memory bandwidth that can be quite useful for running large ml models.

It would be interesting if Apple released models that can locally on your Mac or iPhone and bypass the whole only run these models in the cloud model of the other companies.
I am not trying to communicate anything; just reacting with absolute bewilderment at somebody who is so far removed from reality, that he seemingly has not stepped outside in the past decade.
> There is going to be a broad leveling of engineering salaries in my opinion. The engineer with 8-10 years experience making north of 500k at FAANGs is largely going away.

If those salaries go away, so will the talent. These workers will start new tech companies that either eat away at market segments or end up costing large sums to acquire. You're right that it may take time to replace the salary in the short term.
This, and cloud security, have become my niche at my small company. Keeping these things tidy now will save us so much headache later. It's a bit of a battle fighting product for time but these are hills worth dying on imo.
As a consumer, you arguably shouldn't care. This is a fight between Apple and the App distributors, if it still makes sense for you to use Apple's payment processing then nobody should stop you. However, that doesn't mean Apple can preclude other people from competing with them. Who knows, you (the customer) might be missing out on a better experience because of a lack of market competition. If you aren't, then the App Store still exists. It really seems like a win-win to me.
hmmm. Interesting. I see it the other way around. If the robot's ownership is concentrated in few hands, then there's indeed reason for the mob to arise. If the mob owns the robots instead, then there will be little reason for the mob to raise pitchforks, they'd just collect dividends. Mob can then go vacation in Florida or whatever.
An issue of Amstrad Action had MIDI software on one side of the cassette and a track made using the software in audio form on the other.
Its different. Arguably all 3 is sold at a loss, they make it up with additional game/application purchases. Most game developers are making their games for xbox, ps5, and/or pc. They aren't making it for vr. There is a lack of application development for the metaverse. This is why zuck is spending 13 billion a year. They are trying to make the applications themselves. There's a lack of third party app/game developers
Question for HN: is salmon OK?

I'm serious because I always believed in the no fish rule but then I realized that for me personally, it's white fish where the odor always spreads.

But salmon doesn't seem to spread, to me. No different from chicken. Shrimp* seems self-contained too.

So I'm suddenly curious if other people are bothered by salmon and shrimp, or if it's really just a white-flesh fish thing (cod, tilapia, bass, scallops*, etc.).

* Not technically fish, I know
I'd argue we have no idea what will happen when the glaciers melt, given the lack of accurate climate change predictions to date. We have a lot of models that have historically proven very incomplete with no reason to believe they're any more complete now.

The oceans rising is more a problem, but it's not going to end human civilization and will happen slowly enough that adaptation is possible, albeit expensive. "Drowning" is hyperbole.

Uncertainty is just that, uncertainty. It will be positive for some areas and negative for others. Those of us who benefit from the status quo (myself included) can argue it would be unwise to mess up a good thing, but the simple fact is we have no idea. There will be winners as well as losers. It's quite possible that the midwest becomes wet enough that American farmers will become even more productive through double-cropping, for starters. Likewise the Russians look forward to their northern coastline thawing.

The sky isn't falling, it's shifting, and while we probably should minimize the shift as much as practical, we shouldn't plunge ourselves into an economic depression to do it.
I once build a machine learning library from scratch in rust. No external libraries allowed. It could do linear regression, lasso, and ridge. It also contained some statistical inference features, like p-values, AIC, feature selection. Basically chapter 3 of Hastie [1]. It's more difficult than you might think, as you have to figure out how to do efficient matrix manipulations, deal with floating point overflows, multi-threading, unit testing, bench marking, etc.

[1] - https://hastie.su.domains/Papers/ESLII.pdf
A possible reason is that the layoffs are localized to the tech industry so far, but not all (perhaps even most?) tech workers don't work in the tech industry - they do tech work for other industries such as construction, finance, health etc, either embedded directly or for companies that specialize in providing tech services to them. So until those industries are impacted by the recession they won't see the same layoffs.
Start by owning the datacenter. You might just as well have the data that no one looks at and the 20% load clusters in one, two, or a few 48U racks [1] in the room next to you. Keep whatever is latency-sensitive still on someone else's computer, i.e. the cloud.

[1] Get a "server as they should be", https://oxide.computer (no affiliation)
Glaciers are disappearing globally.

http://wgms.ch/data/faq/_FAQ_RefGlac_Global_Cum_MB.svg
At a large public company— I just don’t do it. Can’t remember the last time I made a slide deck. Has possibly limited my upward trajectory but I guess that’s the trade-off.
Not saying it doesn't work. Just saying that the whole aesthetic is very easily ruined by a few apps.
They do make tools (corvids, octopuses, apes).

Learning and passing knowledge is much rarer, I believe, and I can’t really think of any non-mammal example.
It's misleading if you think of it as an investor filing. Ooh, how are they calculating revenue per user??

Directionally, it's good news. More self-selecting into using Mastodon, hopefully for non-nefarious purposes (advertising, influencing, blowhard-ing), will lead to more conversations.
Eh. For all my kids' daycare career I dropped them off by bike. Given the distance and route it was faster than driving. It really depends on the distances involved, road layout, cycling infrastructure, geography, weather, etc... Not many universals here.
More generally, "there is nothing permanent except change"... (c)
Discontinuous effects, yes.

A stable climate functions more like a light switch than a dimmer switch. There is an "off", and once we go there getting back is really hard. It's almost like a one way switch.

As one example of a feedback loop, when polar ice melts, the area effectively turns from white (ice) to black (ocean). This area then absorbs more heat, driving more heating. So that's one feedback loop.

I think the feedback loops are kind of cool to study. Methane emissions in the tundra. Greenland melting causes more melting. Higher temps cause more water vapor that absorbs heat.

That doesn't give you specifics on where the line is. But wanted to give you an idea about the discontinuity, that there is a threshold vs dimmer switch.

P.S. I plugged your question into ChatGPT but the response was vague.
> I first thought of it as an anomaly, and now I see it as a trend

This has been going on for decades. I was complaining about it back in the year 2001. It is not new.
https://archive.ph/HTtBR
Why is gitea, a self-hosted Github competitor, hosting its source on Github?

Not a lot of dog-fooding going on over there.
Feels like there is a startup in there? Give it your account number, and read only access keys, and it tells you what and where and how to change things.
But it's not BS, automation is essential.

I'd look for other reasons..
Exploring the Emerging Cloud Development Tooling Landscape
Hi all,

This is a very in-depth treatment of the evolution of cloud development tooling from my perspective. I've been working in this space since ~2016ish

Would love to hear your thoughts!
In ancient times, one had to do something interesting or perceived as difficult to build credibility. This involved taking something from blank paper to working program. Yeah, the work was usually overly large and inefficient but people who came out of such “approved” projects were considered (new) members of the community. This was totally separate from coursework and grades, of course, as creation was far more important.

This was usually a super Star Trek game, or an implementation of Life (which led to a fair number of language wars), or a 4x4x4 tictactoe or chess program. One hacker won his spurs making the best checkers program going. More complex projects were binary file editors, system utilities (magtapes pretending to be DECtapes!) or OS mods. Some were lucky to get to an hacking Mecca - these are the ancient heros. Acceptance could not be purchased, only earned and poseurs were ridiculed.

I assume things are similar now, with GitHub replacing card drawers and net based communities replacing f2f. “Because I could” was an amazing goad, particularly when you didn’t know the limitations. Cracking, while useful, wasn’t anywhere near as worthy or honourable. Hackers make neat things. It’s the making not the knowledge itself, and whether the thing is used is a secondary but satisfactory gain.

Decades on, I’ve written miles and miles of code, but very little of it was neat. Useful, commercially successful, yeah, but only a few things here and there made me sit back and smile - these things would have passed muster back then. I hope others get to experience such feelings a few times in life.
Tbh, i think the scripts section is what makes package.json become a mess. It's the #1 reason why packages break and why it takes forever to install some packages. If your package requires building, it's better to just create NPM/package build artifacts ahead of time.
> it also violated the GPL license of DiffusionBee

...and as soon as this was brought to their attention, the authors took out the infringing code and reimplemented it from scratch.
Definitely true during the height if the pandemic. So many paper millionaires when their stocks surged.
> the bike seat cuts off circulation in point where a lot of blood vessels pass through, riding has been linked to cancer

Even if this is true (I'm skeptical without seeing a source), you're more than free to mount whatever style of seat you want on your bike. No one's stopping you.

> Along with the more common city riding hazards like car passangers opening doors, falling over and you breaking bones, getting run over, or even directly breathing in exhaust fumes from trucks.

Great point. Those are all excellent reasons for further reducing the numbers of cars on our streets in lieu of bikes and walking.
Because it's fun, and well suited to the audience.
Way out of my depth! However, the stuff I saw the folks from Oxide [1] talk about comes to mind. Hardware stuff with Rust. If you want to look at a specific project, Hubris [2] is a kernel for "deeply-embedded" systems.

[1] https://oxide.computer/blog/building-big-systems-with-remote...

[2] https://github.com/oxidecomputer/hubris
This depends very much on local circumstances. In our local daycare in Amsterdam, probably 3/4 of dropping and picking up was done by bike. Even at that level, using a car is often slower due to tightness of parking space.
Additionally, attend meetups, present things you are doing as a beginner, let it strike conversations, and let the ensuing experience about talking about something work like be the feeling you leave each other with. In time you'll find something you can bring up with them, or they can bring up with you. Build your network months or years before you ever need anything from it.
I always took "information wants to be free" as a "water flows downhill" kind of statement -- it describes the natural tendency and that you need to do a lot of work against it to contain it, and even then it's probably not going to be fully successful.

It's not about what "ought" or any sort of morality, more of a factual statement of how the world works.
I've been in the industry for a couple of decades. I still don't understand network programming. My knowledge of concurrency is limited. I learned database systems on the job.

That's with an undergraduate degree. Some programs don't cover these things, or they are optional.
Is this really hacker news material? I read a paragraph of this before I decided it was a massive wast of my time. Who cares about such petty bullshit? The only ting worse than "office kitchen wars", is creating an article whining about it.
The model didn’t _assume_ business as usual. It explained the consequences of business as usual.
Mobile home parks offer refuge from Cal housing squeeze. Who’s watching them?
We all want to get to that point where we can watch football on weekends.
Amazon recruiters especially were hounding most of the people I know working in tech.
I wish Rancher had never stopped the development of 1.6. It was such a simple and beautiful tool to run services.

Now they moved to Kubernetes, it has added a ton of unnecessary complexity. It takes magnitude more effort to run anything on it and they call it progress...
> we're probably going to have to see some dire consequences of climate change before any serious action is taken.

Is it your position that there have been no serious consequences of climate change to date? That's not factual.
I have a hard time wrapping my mind around this whole line of discussion because it seems to treat as a binary something that is a continuum. It is not the case that we have "TCP" and "RPC" as some sort of cleanly separable discussion, or at least, if they do mean it as some very cleanly definable term it doesn't seem to have ever gotten a discussion.

RPC, to my mind, isn't really a thing of its own. It's a particular popular pattern for using messages. You can use that pattern poorly or well on TCP. You may need to use another underlying protocol for any of a variety of reasons to get another performance profile out of it. You may be in a situation where you need all the guarantees of TCP anyhow, in which case the room for improvement is somewhat marginal (although non-zero, especially if you want to be on the cell network).

I'm not particularly convinced there's a need or even "room" for a pure RPC protocol, on the grounds that it'd probably end up much like SOAP in that it can only serve a particular set of needs and the benefit of a custom protocol for those needs could well be outweighed by the costs of the stampede of developers jamming everything into the new protocol regardless of their needs, most of which would mismatch. The field of "RPC" is already very diverse and to my eyes, people generally have satisfactory solutions available to them.

It's not like it's even possible to build something that would both replace generalized RPC on the internet and service supercomputer mesh networks.

If TCP was the only option, yes, many needs would be going unmet, but it already isn't. If I do an analysis and determine that TCP is my core problem, it seems to me I already have an abundance of choices serving many points on the continuum. I don't see what trying to lift up one of those points as some sort of standard would particularly accomplish that isn't already being accomplished in the real world. And it isn't even RPC qua RPC driving that per se; you can have all sorts of niche needs that drive you off of TCP, of which RPC doesn't even strike me as a particularly distinguished case.

RPC when you get down to it just isn't that complicated or really even that interesting; you send a message, you expect a 1-to-1 message back in reply. Of all the message patterns, it's just about the simplest other than unilateral broadcast without any reply at all.
The way this was handled where I went to school the DB class was basically presented as a history of database technology class where the CS fundamentals behind how each type of database works, what it's weak points and strong points are, etc..

SQL was then something that was a side thing in the class that you were supposed to pick up for one of the projects.

We had to learn to normalize schemas in that class. I have yet to come across a team in my career where normalization was understood well enough to where it could be correctly matched to the architecture of the entire system.

The other amazing takeaway was going through the historical failures of hierarchical & graph databases. Since I started working hierarchical databases have come back with tons of hype twice now (once in the late 90s, once in the late 2010s). Both times they failed exactly the same way as history would predict based on what happened in the 60s and 70s that led to the development of relational databases. Sometimes it seems like the industry hype train is completely unaware of computer science.
Yeah. I can think about consultants making $$ giving full analysis of cloud costs and ways to reduce them. It's actually not very technically challenging TBH. All those low hanging fruits can be grabbed by a junior enginner or even a non tech senior person who is a deep user of such services.
> Correct and extensive technical specifications are as hard as the code/stack itself.

Yup. Maybe even harder.

Ditto requirements gathering, analysis, acceptance testing, adoption (evangelism), etc. All that squishy organizational psychology stuff.

Coding is the easy part.
"Driving without due care and attention" sounds like a statute that has a much more specific interpretation than you think, and the police probably aren't the ones who misinterpreted that here. "Careless driving" and "reckless driving" are against the law in many states in the US, but both actually have very specific interpretations that are not entirely contained in the text of the statute. This is the joy of living in a common law country.

Things like running red lights, not stopping at stop signs, and speeding are much easier for laypeople to judge, and it sounds like none of that was happening here.
If we take a person from a prehistorical hunter-gatherer society, you are either a trained and physically fit human, or a dead one.