skysight-inc/HackerNews huggingface dataset:
Reserve | Great time to join crypto!!

ICYMI, turns out the "most exciting project in defi" was a giant house of cards and collapsed. Consumer crypto lending platforms that were gambling on it are now insolvent and tons of normal users are screwed.

But hey, with prices collapsing and tons of scam projects getting flushed out, we forecast 12-15 months of reduced bullsh*t in the industry!!

Here's why the collapse happened: https://www.youtube.com/watch?v=GTBBBy7IYhI

Our timestamped prediction: https://twitter.com/ReserveLodge/status/1260479326065176576

Background for normies: https://www.youtube.com/watch?v=3KZY41SqaTI
It would be sort of funny to apply some reordering algorithms to the dependency graph, and use that to refactor a project. Maybe nested dissection. Or some fancy hypergraph reordering...
Any symmetrical distribution will have the mean equal the median.
True, few cases go there, but the recent decision means, that there is no such thing as "settled law" anymore. The Supreme Court may change its oppiin on any thing, thus on lower courts it's harder to say "see, there was that decision, we follow it" but there is more freedom to derive from it.
>Or you just manage state in the server. With https://inertiajs.com/ you can even afford to not to declare an API and still manage the state back there.

Then we can party like it's 1999!
hate to inform you it is tiktok
There’s a lot of future.
No vapes? Seems like a good crossover market for DIY inhalers (or whatever vape machines are called), especially if they're already comfortable selling tobacco.
We Need to Do Hard Thing
Went down a rabbit hole exploring the links on this blog. Engrossing stories, and I will never tire of story trope of the small company with a chip making an impact by following their own beliefs
I agree with the thrust of the post, but I find myself a little trapped by lock-in. I'm not any kind of famous, but I use my name on GitHub, and I have shared gists and repos pretty widely with people at work and online. It's a place people can easily find me, to see what I do, and it's tough to move away from that. That said, I have moved a few repos over to GitLab (which is also imperfect but better) and I will definitely give Sourcehut a try at some point.
I use 'save to Wayback Machine' and SingleFile.
The VaMPiRe iOS Architecture (Part 1)
Yeah it’s definitely annoying thinking of what to eat everyday, i especially hate spending money to eat two bites and not want to eat at all after.

I’ve been trying to train my body to get hungry at “normal” times. I kinda hate breakfast, always have, but now I’ll eat a piece of fruit i enjoy in the morning. Later on in the day I’ll try and eat something else that’s small and i enjoy. My thought process is that if i continue to do this my body will start to crave food at that time and my appetite may come back.

I’ve had varying degrees of success so far, i don’t have the habit of the small healthy snacks yet so i keep having to remember. I think i may set up a bot to text me to eat at X time.

The depression definitely doesn’t help, hard to motivate to eat when you’re low. Dealing with that in parallel should help. When i can exercise again I’ll probably start doing that too for 30 minutes a day to build up an appetite.
I have no religious affiliation beyond accepting others’ religions (I’m not atheist because ultimately atheism is overly restrictive in its worldview) and agree that abortion is way more nuanced than what modern feminists present. Personally, I’ve been on both sides of the spectrum at different points in my life. I believe I am now somewhere in the middle and the reasons are not in any way religious. They’re based on my lived experience more-so than high school ethics. But man the amount that people want to reduce this to “fuck religion” is really annoying. No one wants to admit it’s a yucky issue.
> Does it solve the problem of only redrawing the required minimum (beside the normal VDOM approach)?

Yes, in fact I think it's actually pretty hard _not_ to redraw the bare minimum LOL. If you want to know more about Svelte (even if you're not looking to develop with it) I HIGHLY recommend listening to this presentation called "Rethinking reactivity" by Rich Harris (the creator) https://youtu.be/AdNJ3fydeao

> But does it solve the problem of growing state which never gets GC'd when components which used to use it are gone?

I think the answer to the question is yes. Although the problem I'm speaking mostly about state management is the source of truth problem. Svelte provides a global store to store data, and data stored on local components are just _variables_ (no useState or hooks or anything complicated) where the Svelte compiler handles everything.

Something else I'm really eyeing right now is SolidJS which takes a very similar approach to Svelte (compiler instead of library) for frontend development but provides an API that's very familiar to React developers so there's not much of a learning curve (although Svelte has a very easy learning curve too).
Streak (YC W22) is hiring customer success specialists to delight users (remote)
> middle ground between blind praise and mob bullying

It's spelled out in the HN guidelines; if you see violations, then downvote/flag.

In 2015, a new guideline was added; it's still right at the end:

"When something isn't good, you needn't pretend that it is, but don't be gratuitously negative. "

https://www.ycombinator.com/blog/new-hacker-news-guideline
Reflection is killer for performance because it brings Java/Go down to the level of a JIT-less language like Python (and ORMs aren't too kind to JITs in e.g. Ruby/JS either). The problem with reflection in Go/Java is mostly that it's hard to read, since the reflection-ful APIs are hosted rather than native syntax.
I guess that depends on your definition of the word "natural". But one of the notable characteristics of nature as it actually exists in our universe is that its behavior is governed by discernible laws with very low Kolmogorov complexity. This is what makes science possible. But the universe doesn't have to be that way. Harry-Potter-stye magic could exist in principle, and that would be different enough from nature-as-we-know-it to deserve a different label despite the fact that magic would, in such a world, be "natural".
ShotSpotter is a private company that is 100% dependent on police for their business. It's a relationship that is bound to end up corrupt. Whenever ShotSpotter makes the police look bad, they'll end the contract.
Very Good.

Diem, Libra and Novi. A complete waste of time, absolute failure and another gigantic nail in the coffin for crypto.
>much less scientific than macroeconomics or inflation management

That bad, eh?
I am cursed to be about eight-ten years ahead of the industry on development philosophy. Half the stuff I was begging people to do in 2005 was de rigeur by 2015. People who are trying to catch up with the last things they weren’t early adopters for don’t want to hear about the next three things after.

And they sure as hell don’t want to hear about how much of our difficulties with software come down to self delusion and misplaced optimism. Or how that new tech is old tech with a coat of paint and how it only lasted four years last time.

I don’t often win this argument until after something really bad happens and everyone is looking for a deathbed conversion. Until then I’m just some weirdo street preacher. So no, I’m not going to share all of my opinions with people I just met. Unless I’m specifically trying to fuck with them.
Slack’s mobile team uses a variation of VIPER.
If I was applying at let's say Enron or [REDACTED], I wouldn't exactly be comfortable giving my opinion of their business model according to my values. I mean, that's why I don't work at any of the [REDACTED] companies, but to each their own.
Who had Voyager Digital next in the DeFi dead pool?
As a lawyer, this is one of the most insightful posts on the practice of law - in so few words - I've ever seen. Bravo.
The priest and the dying soldier, 1962 (2021)
Digital Ocean has, bar-none, my favorite dev docs on the internet.
What kind of _small_ computation are you doing that requires 50 whole milliseconds?
By that logo , SpaceX shouldn't exist.
What I pointed out through a rhetorical question is that the article's first sentence tells others their opinions of open source are limited, but the premise of that statement is that the author is separate from that rule and by the act of writing this statement is setting a broad opinion which others are not allowed to have, due to the same statement imposing a limitation on them.

I was pointing out that the first sentence of the article contains a contradiction in its premise.
They're quite powerful if you aggregate in a tool like Splunk, ES, or GCloud logging.

You need good quality logs though. Because noisy useless JSON logs are even more noisy and useless.

Agreed on the one key per line bit.
This isn't a "great lawyer" play . It's the standard play for any unscrupulous party engaged against a party with limited funds.

Even if a case is pretty open and shut, you can tie it up for years in motions for little benefit. This isn't hard at all.It's hard to be on the other side and respond to it.

A great lawyer can achieve a settlement against a party like this without the need to throw sacks of cash onto a firepit.
Not often I give props to the BBC, but impressive how they've managed to keep that page/article working for so long. Even most of the links on the page still take you to somewhere relevant and the search box still works.

Surprised they haven't bothered to try and migrate the old articles to their newer systems though!
Breaking Down Wimbledon's $350M Business
Is it education or the time and money that is needed to get this education?
Not to mention that a costly education runs the risk of becoming useless after parental leave, especially for women.
Nowadays many people have to decide between family and career
Justice is great for those who can afford it!
Looks pretty interesting, I'm always kind of bothered about the lack of (true) full-stack frameworks for the NodeJS ecosystem that handles accounts, database, frontend, API, etc. like we have for Python with Django or C# with .NET.
Bud author here, thanks for including Bud on your list. That's a really good overview of the landscape!

My take is that Remix + Next.js + SvelteKit are going to continue to innovate fast in the Frontend and "Backend for Frontend" space. Rails and Laravel don't hold a candle to the experience you get in that ecosystem.

But the JS ecosystem is massive and, as a result, fragmented. As you mentioned, there's no consensus on ORMs, mailers, queues, etc.

I don't see those frameworks trying to push too far in that direction, they'll remain "UI focused". This is nice for their focus, but not great for someone who wants to launch a web app and doesn't want to figure out all the surrounding ecosystem tooling.

This is where Laravel, Rails (and soon Bud) (and I assume Copper) will shine. They provide more tools and interfaces out of the box for building full-featured backends. These frameworks definitely need to keep an eye on the best ideas coming out of the JS framework ecosystem though!
FWIW, the term "thunk" is a long-standing CS term that long predates Redux [0] [1] [2].

In fact, my first job back in 2008 involved a C++-based emulator/VM framework, and the devs used "thunk" to refer to jumping from the original program binary out to altered/replacement code written as C++ to add additional behavior or replace functionality.

"Proxy" is also a long-standing term as well that describes wrapping or replacing functionality of a system, which is why it's used for HTTP servers and why it got used for a new JS capability in the ES2015 language spec.

[0] https://en.wikipedia.org/wiki/Thunk

[1] https://stackoverflow.com/questions/2641489/what-is-a-thunk

[2] https://devblogs.microsoft.com/oldnewthing/20081020-00/?p=20...
> Maybe because it feels like taking a small, simple thing and making it seem like it's something more.

Perhaps it makes more sense to treat frontend engineering as thick client desktop development of yore. Websites are no longer small, simple things, they are now the primary apps that many people use (through the broswer and especially through Electron), so there needs to be sufficient tooling around managing that complexity.
How is React not solving essential problems? Suspense solves a pretty essential issue. Also Svelte can quickly increase in bundle size and if you have enough components, it can become bigger than the equivalent in other frameworks: https://github.com/yyx990803/vue-svelte-size-analysis.
Alternative front-end for Genius.com without the clutter
I disagree with a good part of the substance of the article. Publishing open source software incurs a self-imposed obligation to do much of what Mr. Hickey says nobody is entitled to, in my opinion. If you don't want that responsibility, don't publish.
CD and more – save time with powerful terminal navigation on Linux and macOS
I chalk 50% of it up to general anti-js and anti-web attitudes. It's another easy target, a sign that, oh no, there's a place that isn't well groomed, well tamed, well under control, like- as this gist proposes- the safe secure well-patterned language with only a couple frameworks that I use is.

It's crazy to remember though that Backbone was introduced in 2010, largely credited as the first JavaScript framework. And there was indeed a manic cambrian explosion, a half decade of more more more. And a lot of the ideas were only part-way baked.

There was a thread on Why Devs Cant Sell[1], and I think some of what I said there[2] applies here. (Geeky) devs are high-context creatures, and businesses/industries/fads push us to higher-level, more cookie-cutter modes of production. Geeks should have curiosity & want context. What are the tradeoffs? Where are the weak spots, places we haven't explored?

It's murky what we are buying into. Too many frameworks, imo, Sell, and not enough inform; they don't target the alpha-geeks taste-makers that would relish being fully briefed in how it got built, what the tradeoffs were, what actuation points there are under it. A lot of these frameworks look like they're being sold to suckers who are ready & raring to go swallow the marketing grade swill, rather than to intelligent & smart folk who will understand & properly appreciate what they are "buying". From a comment[3] in a thread on new breed of JS state management libraries:

> The reality is that the community hypes certain tools, but in practice, they tend to have gotchas buried far beyond the surface level demos and documentation. The problem with that is that you only figure that out after committing to those tools and using them. This leads to tool abandonment, or in some cases, developers taking a swing at their own version. What they come up with is more often than not a rehash of the old ideas but lacking any "why" or long-term vision.

Where-as libraries tend to solve distinct & clear problems, Frameworks outline a whole dwelling for your app, and the bounds of use are going to be very wide. It's taken millions of developer-hours to suss out & explore React, with various phases of exploration re-figruing shit out again and again (Render Props, Higher-Order-Components, Hooks, State Management). Having a lot of communal, shared learning time is incredibly important. But figuring out how to get that battle testing, how to understand the real merits & problems with what we create, learn where things do adapt & fit & where they are course or stiff or not fitting: few projects even attempt an earnest portrayal, have material to list, explore what context they do cover, much less indicate, Here Be Dragons.

[1] https://growthlab.so/why-devs-can-t-sell https://news.ycombinator.com/item?id=31936015 (36 points, 1d ago, 15 comments)

[2] https://news.ycombinator.com/item?id=31936177

[3] https://news.ycombinator.com/item?id=31960694
I'm used to seeing the picture of him as a younger man.
Ask HN: What will tech look like with less job mobility?
Suppose the bubble bursts, and we enter into a recession or some sort of "tech winter" where the flow of dumb money ceases and it no longer becomes as feasible to job hop every 1-2 years, as it has been in Silicon Valley and other hot tech markets for the past decade. In that situation where tech workers end up staying at their companies for longer tenures, how will the shape of the industry change?

Will both workers and employers act less transactionally towards each other? Will there be greater loyalty from both sides? Will projects be planned out in a more long-term fashion, rather than chasing quick returns? Without the same hope for a quick exit, as in the past decade, will companies try to build more sustainably, rather than blitzscaling?
We Could Discover New Particles Around Black Holes Through Gravitational Waves
Games Done Quick “Ocarina of Time” beta showcase
If you get a 1U mini-itx case, you can put pretty much whatever in there. Finding a heatsink that fits will be a challenge, but they're out there. Expect thermal throttling (or set a low power throttle, which is inline with your desire to reduce watts anyway)
oh yeah good call.
Thanks for the suggestion! It was an interesting read for sure.
Composting is bullshit until we’ve mandated that produce stickers be fully biodegradable. Nothing put me off city compost like finding microplastics everywhere in the pile.
Thank you the suggestion :D
I don’t know it must be people dependent I guess. I was in the same situation distance wise from high-school than you also in the French countryside and it was some of the easiest of my life.

Workload is low. You don’t have much courses. The material is easy. I was an awkward teenager but all in all people were pretty nice. I don’t really have a complaint about high school.

Prépa was annoying however but mostly for the pointlessness of it all. Looking back I probably should have left to do something else after the first year but I can’t deny it was a good choice for my career.
I am curious about your comment. What new languages have you seen that are not memory safe by default?
So it’s a meme-Ponzi-scheme-crypto-rugpull? What makes it different from all of the other ones?
From my experience, people think most people back then lived around 40 years, while some lived less and some lived more.
if you viewed it on an 800 x 600 screen, it would look appropriate
Sure, and there’s nothing wrong with that…let people have their fun?
27 out of 31 reactors being built since 2017 are Russian or Chinese designs
Censorship is the norm practically everywhere EXCEPT the U.S.
Ah, I see: https://slack.engineering/scaling-slacks-mobile-codebases-mo...
Information hierarchy is extremely underrated.

It’s surprisingly hard to do which is why these days so few do it, plus screen real estate on mobile adds additional challenges.
Association Between School Mask Mandates and SARS-CoV-2 Student Infections
It's also not especially performant to do the naive (i.e. short) implementation like this, since you'll likely end up parsing/processing path elements left-to-right rather than in whatever order makes the most sense for your loading.
A few different problems...

"Necessity is the mother of invention" comes to play here. The reality is that the community hypes certain tools, but in practice, they tend to have gotchas buried far beyond the surface level demos and documentation. The problem with that is that you only figure that out after committing to those tools and using them. This leads to tool abandonment, or in some cases, developers taking a swing at their own version. What they come up with is more often than not a rehash of the old ideas but lacking any "why" or long-term vision.

The other one is employability by obscurity. An old grifter trick is to make something far more complicated than it needs to be as a means to guarantee employment (both on the tool developer side and the end-user side). For the tool developer, the more they can twist and turn their tool (introducing novelty and potentially confusion), the more sought-after their services will be. For the end-developer, they can hold a "monopoly on intelligence" and become difficult to replace in a company because they're the only one that understands that thing. Couple this with the conference talk circuit where you see the same people constantly pitching some new-fangled widget every year and you realize the goal isn't to solve the problem, it's to get paid to look like you're solving the problem.

Another problem is inexperience. A developer might have just enough experience to feel confident at the code-level, but they lack the practical experience to let them know why a certain pattern is incorrect. Assuming that they never get that practical experience, they will continue to iterate the tool into an utter mess or deprecation.
I think Wikipedia references are encouraged to use archive links because it will show the page at the time that they used it as a reference as opposed to linking to the live page which can change at any time.
> Because on one hand, the judge believes himself to be bound by conventions and norms, the gravitational force of precedents, and the judge’s internal sense of what ought to be the result. On the other hand, these forces battle against various social forces and structural realities that are far more real than the canons about how you read statutes. Every judgment is the outcome of such a conflict.

Fascinating and excellent point, but I think I'd suggest one nuance to this interpretation. It works this way everywhere, but perhaps in India, the rule of law is in direct conflict with social norms, whereas other countries with rule of law have managed to align law with social convention to avoid this problem.

Imagine a judge interpreting a law that, for example, clearly assigns the death penalty to a child.
Desalination is when you have salty water and remove salt.

Processing is when from some state you get a different one - here, your system already starts from "the different one" found in nature.
I'm sure the ability to do so is buried in 50 pages of terms of service.
> React/Vue devs

devs probably not (ie: as NoSql, Kubernetes and stuff, some people pick overkill things, and by some I also mean me!), but React/Vue as libraries, certainly!

A SPA is a niche among the most mainstream web site. It makes sense when the interactivity is BIGLY on the cliente (like for example: A paint app).

But most things on web are not 90% client vs 10% server. Is the opposite.

Your todos, mail client, eCommerce site, blog, etc are better served with a server-side approach (note also how much important security is on this kind of apps!).

Your screen that display an interactive map, your game, paint app must certainly need a more client-first approach.

But as SPAs says: Is a "SINGLE" app. One.

Is your full app ONLY ONE? No? Then you are not in the niche, and if you actually have that SINGLE screen/app is likely a fraction of the whole thing.

---

Another possibility is that single thing consume so much that you say, screw it, lets do the rest similar even if is a poor-fit, but I think that is rarely if ever the best (for the users!). This is what drive adoption, React/Vue solve nicely some hard stuff and naively you think is great for the most basic one. But as show the fact that stuff like "back button" get broken without EXTRA workarounds is not the best fit for them...

P.D: Is my opinion -after try for years do the opposite!- that the majority of the web apps be server-driven and maybe add a little of react/vue/alpine for extra nice touch...
It's not so much larger data than it is analyst velocity.

Polars runs orders of magnitudes faster than pandas does. Which means EDA can be completed quicker.
It's not even necessarily the same information, but small pieces of one bigger piece that need to be updated once some of the other smaller pieces change
Agreed! And in any case, if the company culture doesn't suit the OP, assholes or not, don't stay. This can be a huge energy leak. I realized this only too late at one of my previous jobs.