skysight-inc/HackerNews huggingface dataset:
Yeah thats why I'm keeping one eyeball on Gleam[1] which is a 'statically-typed Erlang/Elixir', when that hits 1.0 that's when I will put down my F# SAFE stack stuff and give it a try.

[1] https://gleam.run/
I think a lot if datacenter SSDs already come with in-drive hardware compression these days, since it not only increases speed but also longevity. So it would actually save money anyways.
In short, contribute to the community by posting comments that get voted up. Once you pass a certain Karma threshold value, and I'm not going to explicitly state what that is, start posting interesting submissions.
It's worth noting that the only real competition in that market at the time was Hipchat, which Slack eventually bought.
None. It created, however, the problem of non-qualified amateurs being able to hassle experienced professionals.
Yes, the USP of Slack is that you can close it down when you're done working for the day. It does nothing better, or much worse, than any other social media chat application, except it wraps up work in one button press.

Not sure how you could monetize that but hopefully the Slack staff doesn't know either.
One of the most interesting applications of ODEs (in my opinion) is the field of control theory, which empowers autonomous systems/robots/vehicles to guide themselves. Brian Douglas has some fantastic introductory videos on the subject [1].

I don't think I agree completely with section 5 (Forget About Existence and Uniqueness of Solutions). For an ODE in the form xdot = f(t,x), existence and uniqueness on an interval follows if f is continuous in t and Lipschitz continuous in x [2]. This often isn't too difficult to demonstrate for a given system. In addition, if you can't prove uniqueness of solutions then you likely have to treat the system as a differential inclusion [3]. I personally find differential inclusions fascinating, but the math can be much more dense.

[1]: https://engineeringmedia.com/videos

[2]: https://en.m.wikipedia.org/wiki/Picard%E2%80%93Lindel%C3%B6f...

[3]: https://en.m.wikipedia.org/wiki/Differential_inclusion
Sylver – Intuitive JSON AST Queries
Slack was everywhere, years before Discord was in common use. Discord, really, was just Slack for gamers - but more importantly, it was a replacement for Teamspeak and self-hosted forums.
>. They charge by the GB and are not exactly super cheap so if the customer wants to store a big fat file of easily compressible zeros then whatever, they got their money.

Maybe they charge at uncompressed rate but store it at compressed? Then they got even more money!
My focus has been heads-down on product not on YC.
But realistically I think it's a huge advantage, even if the plan remains to build the product either-way.

For example, if I didn't have my "other job" of running my other company I would be able to go a lot faster.
Perhaps worth mentioning that the Phoenix creator Chris McCord has written a number of posts on the Fly.io blog since he joined them a year ago (exactly a year today?):
https://fly.io/blog/how-we-got-to-liveview/
https://fly.io/blog/how-safari-ruined-my-tuesday/
https://fly.io/blog/livebeats/
https://fly.io/blog/liveview-its-alive/

I guess that’s part of the reason why the Phoenix blog is less active?
A better approach is to declare certain web tech as public utility, like a search engine, there has been zero innovation that has changed the marketshare.
Solar briefly overtakes coal in Australia as number 1 source of power nationally
Honest question: What must-haves do you need YC for? Sounds like you’ve already learnt the hard lessons and you’re on the right track.

If you need cash then go and pitch some investors. Either you’ll get some cash or you’ll get a reality check. Both have value.

Being outside the US doesn’t stop you pitching US early stage investors and then flipping the company to move there (if that’s something you want to do).
Does it actually, though?

In practice - aren't tax rates changed based on politics?
True in the sense that you mean and alao in pure CS theory terms but also the TFA also links to some serious documentation on practical solutions to many real world performance problems and browser codebases have most of the underlying complexity for other less obvious performance issues. E.g. https://github.com/Igalia/explainers/blob/main/css/has/has-s...
Yet apple released a $6000 mac pro (that when fully specced, came out to be ~$60000, iirc), a $5000 monitor that competed with monitors almost used exclusively by Hollywood production houses and an optional $1000 stand for said monitor.

I guess that was 2019 and things have changed?
> That said, is there a reason not to use relative imports?

Yes, they make reading imports across your entire project rather difficult: Suddenly there are multiple ways of referring to the same module. If you ever have to do a project-wide search & replace during a refactoring (because your favorite refactoring tool failed you), this will be hell.

Moreover, in each file you'll end up with a weird blend of absolute and relative imports, depending on what was shorter or looked nicer to the author at the time. Not nice to look at at all.

> This led me to dig into why we might add to __init__.py

…or why we might rather not. Init files are one of the main reasons imports in Python often behave in unexpected ways. As a library user I do not want to study the library's init files first, but unfortunately I often have to in order to understand what is going on. (Case in point: Tensorflow 1/2. To this day, I can't claim I understand how exactly their init magic works and time and again I get bitten by failed imports.)
How would that work for something like S3 range requests? Rather than reading an entire object sequentially (which would work fine with transparent compression) you can also ask to read an arbitrary byte range (give me bytes 1,000,000,000-1,000,001,000 from the original file). I guess you could maybe store the compressed file in chunks with metadata about the original byte range inside each chunk.
Note that Slack was not the only or first software-as-a-service solving this problems. There were others, some even earlier. E.g. Flowdock https://www.crunchbase.com/organization/flowdock

Slack led the markets with best execution (maybe?) and good funding. Until Microsoft came around with its own unique non-replicable assets and skills.
They’ve spent 20 years working with idiot management what do you expect. That said I wish the ones I worked with were risk averse and stopped launching kamikaze projects to nowhere.
'Waste'? Like the New World would have been 'wasted' by the native peoples living there?

There are so many false dychotomies and assumptions in your comment I do not know where to start.
First, thanks for the advice. :)

You are right I don't actually need YC. But it would make things faster. So any advice on the best way to approach it would be useful.

I'm worried that they will write me off since I had a first interview 10 years ago.
https://archive.ph/jImGZ
Because the resources other than energy are finite.
The Method Resolution Order (MRO) is firm and documented. It's just not something anyone keeps in mind unless you use multiple inheritance a lot.

Conflicts are determined by the MRO. If some classes don't call super(), then they won't call super --> classes further down the MRO won't be called and won't be initialized.

The choice isn't: multiple inheritance or a couple lines. In the right situation, multiple inheritance could save hundreds of lines and condense a complicated mechanism into a simplistic one. Used flippantly, they can be a nightmare -- but that's true of all programming paradigms.
It’s been depressing watching what has happened to India since Modi came to power. The veneration of Gandhi’s assassin by the BJP says it all really.
An uncrewed boat, controlled from the UK, maps underwater volcano in Pacific
I'm surprised noone has written "Death Stranding" in the comments yet.

Death Stranding.
(and how easily you can fudge numbers of active users if you force install Teams on every Windows 11 machine and force it to run in the background, same as ignoring browser or search engine preferences and always force Internet Explorer Edge and Bing down people's throat until they suffocate in it)
No, the main reasons to vote for or against an infrastructure project would be its utility (how many people would take it, what things it will enable, how many people would take it instead of a car or plane and the benefits that will bring), not how good it is at estimating costs.
> Nothing that IRC doesn't have, but they sold it better.

I think that's really underselling Slack, between threads, attachments, code snippets, reactions, etc.

For example a Slack pattern I've seen multiple times is teams offering an help channel for their internal users, with one thread per question, and using reaction icons to track which have been answered. It works amazingly well even with thousands of users. I like IRC, but I think it would be really chaotic in comparison.
If it's funding you need, make sure to look more widely at the options. There may be local investors in your region, or you could pitch to American investors who specialize in your vertical.

Thinking you must get into YC to focus on your company is like thinking you need to get into MIT to learn calculus.
Zero predefined structure
I don't have an issue with unix but I still rely on being able to work in scenarios where I don't have a reliable/fast-enough internet connection to be able to run multiple hi-res GUI desktops remotely. If we get to the point super-low-latency network connectivity is as available as electricity, then sure, it's feasible. But even 30ms latency can make GUIs feel clunky to work with. I know some devs seem to tolerate it though.
In reality, it works like Los Angeles and The Bay - and everyone who (owned) and gets priced out ends up with a massive windfall at some point.

How massive depends on how long they stay into the boom.

Again, no one ever loses (financially) from prices going up.

All you get are options (financially).

If your home is direly important to you, and being close to family is important, too - you still have options.

1) Sell and move in with family and use your gains to help offset their property tax

2) build an ADU in your backyard / convert your garage to an apartment - and use the rental income to pay your fair share of property tax - plus have the majority left over for spending

3) continuously cash-out refinance to pay your property tax + your previous cash-out

No owner loses (financially) from property prices exploding.
In my experience, the best founders who show up here on HN are product driven people who are eager to show their idea and prototype. Here are some off the top of my head:

Brian Armstrong:
https://news.ycombinator.com/item?id=3754664

Drew Houston:
https://news.ycombinator.com/item?id=8863

Peldi Guilizzoni:
https://news.ycombinator.com/item?id=238772

When I read those 3, each time I had the strong feeling something would come out of it. And each time it did.

Your post leans rather on the "I have a great, secret idea and team" side and features a lot of social proof and other convincing arguments. Your early career success, how much "monetary value" you invested etc.

This focus on tools of communication will probably also show when you present the actual product. My feeling is that more focus on the product itself will help you to get further.
Slack made it easy and fun to connect with your coworkers, it wasn't unique, but it was a right time sort of thing.

We had chat systems before like IRC, Hipchat, Campfire, Flowdock (We have used them all), but with Slack it was the first time I felt a push from other departments to use it.

I'm still sad about the implementation of threads that Slack went with, Flowdock did this much, much better, every new post into a thread were also posted in the channel view but with a unique colour, the interaction can be seen here: https://youtu.be/BxRE5GUbFes

I also liked that Flowdock had the concept of an "inbox", so every channel had their own inbox for integrations that wouldn't post a message and notify everyone, but you could still chat with your team about a certain item in the inbox.
Sounds like a good one for r/askhistorians.
Westerners totally fail to appreciae,that once you replace all houses with, say, 6 story apartment of equivalent internal area, you gain so much space outdoors.

The single story suburbia looks claustraphobic - instead you have soace for parks, public squares, and services and facilities. There can be large distances between apartment blocks, and can be very green
Perhaps you know since you’ve read the book: Does the book _really_ decide on declining marginal returns to complexity as an ultimate factor? Or is that the interpretation by the reviewer? The bridging of sociology, history and economics was somewhat rare back in the 80s and before. (Douglas North a notable exception, obviously not alone.) If the author does, now I’m wondering why I missed this book & going to read.

First thing as a counterpoint that comes to mind is biological complexity. There are marginal diminishing returns to complexity in biology as well, but not a rise / collapse rhythm in biological complexity outside of external events that I know of.
Show HN: An attempt to make a reduce-palette/dither filter for 2d canvas images
> But then came the physics class, why we could go from dy/dx = f(x) to dy = f(x).dx and integrate both sides remain a mystery.

That is just integrating both sides with respect to x, but you're skipping the step that makes that clear.

Start with dy/dx = f(x).

Integrate both sides with respect to x: ∫(dy/dx)dx = ∫f(x)dx.

Doing the integrals produces: y = F(x) + C, where F(x) is the integral of f(x) and C is an arbitrary constant of integration.

Above, the integral on the left doesn't do anything except cancel the derivative. A similar but more substantive method is solving a DE by separation of variables, where the "mystery" is integration by substitution (a.k.a. the chain rule backwards).

Start with dy/dx = f(x)g(y). This is a "separable" DE.

Rearrange to (1/g(y)) dy/dx = f(x).

Integrate both sides with respect to x: ∫(1/g(y))(dy/dx)dx = ∫f(x)dx.

We are integrating with respect to x, but where is the x in 1/g(y)? It is hiding inside the y: y = y(x).

Define a substitution: Let u = y(x). Then du/dx = dy/dx ⇒ du = (dy/dx)dx, and our equation becomes ∫(1/g(u))du = ∫f(x)dx.

Do we really need to introduce another variable? No. We can just use y: ∫(1/g(y))dy = ∫f(x)dx.

We often jump straight to this point which makes it pretty confusing, as it looks like we're doing different things to each side of the equation.
Well if they figure they will get more customers to offset lower profits they’ll reduce the price. On the other hand if they think they can double the price but only lose 10% of customers they’ll do that

It’s econ101, the cost of providing the service doesn’t really factor into the price charged, what does factor in is the cost of alternatives (storage from azure, backblaze, on prem, not doing it), and the risks (increase s3 costs and people might realise they are being ripped off on ec2)
You're right... YC isn't a "must have".

But YC clearly still has value. For me specifically it's about speed. It's not like YC itself is some North-star, but I think it would speed things up a lot.

Also very specifically: it would mean I can quit my "other job" running my other company and focus 100% on "Act 3" instead of splitting my time.
If you switch to Georgism without fixing zoning it ends up worse not better. Zoning my land as suitable for a high-rise can destroy the entire value of my home because it becomes an unusable structure due to the higher rates of tax. At the same time zoning my land for high-rise causes the value to go up and that results in a massive tax increase that eliminates any price gain for my land. Since I so firmly don't want my land to be upzoned I become a NIMBY and compromise with my neighbors to also protect their land from upzoning. We all elect politicians that oppose all upzoning. Some Georgists argue that I'm supposed to want my neighbors upzoned because it raises my CD but they seem to have not done the math because if you're applying the CD over the entire US then upzoning a single neighbor raises my CD by fractions of a cent which I care so little about that it doesn't change the incentives for this political alliance.
This has been an issue forever (I have a similar blog post from 4+ years ago tracking down the exact same issue: https://cmetcalfe.ca/blog/diagnosing-periodic-high-ping-time... ) and I can't believe it's still not fixed.
zstd not good for everything. Yes, it's fast in terms of compression. Easy & fast you can make compressed archive. But if you need to use the zstd on daily basis - i have bad news. ZSTD not suitable for general purpose archiver.

Depends on the data - you can have totally different output compressed archive if compare to winrar for example.

Example:
I doing backups time to time, and archive important files into compressed archive containers (rar / 7zstd).

I've noticed, that my dev folder with tons of repositories, images, and different work related fines - vary damn too much.

/dev/ size = ~11GB

rar output (normal compression) = ~2.1 GB
zstd archive output (normal compression) = ~4.7GB

Why?
linked files, same files not treated as a 1 file + links to these files. Instead these files compressed each 1 by 1 instead of copy 1 identical, and compress the file. And many things like that.

Suggestion for 7z-zstd -> add ability to save links to files, not treat them as separate files, and adding an option like in winrar to search for identical files first and re-link all of them and remove duplicates, instead of compression each.
The same president that made bitcoin El Salvador's legal currency also managed the growth of the economy and its response to the Covid-19 pandemic. Nayib Bukele is the most interesting politician in America today.
> it’s crazy to see how much effort is duplicated and coordination needed even in cases where there’s no public api necessary.

Probably because they decided to use microservices (read: distributed systems) for no God-loving reason.
Don't worry about it, no damage done.
Doesn't have to be like that though. I've got a rack next to my desk and it's fine noise wise, though less fun during summer (no AC here)
Generally speaking, if it can be done in the client, it should be done in the client.

Phoenix.LiveView.JS aims to tackle the obvious cases but it also documents a pattern that I tend to use a lot in my apps: https://hexdocs.pm/phoenix_live_view/Phoenix.LiveView.JS.htm...

The pattern above has a benefit that the dispatch still comes from Phoenix, so you are not relying on IDs or query selectors to attach functionality. You can see how we use it in Livebook here: https://github.com/livebook-dev/livebook/blob/main/assets/js.... However, if the callbacks get too complex, then you may indeed want to test them via headless browsers.
It’s extremely common in college (American) football to mention that a player’s family is attending and often cut to showing them. I’ve seen it in NFL and MLB games as well.
Did you read the communication from before it was implemented? The largest talking point was getting money from El Salvadorans living outside the country back home (because the traditional banking system is failing them), not making capital gains from BTC.
> if you’re still alive you can always die another time

Well, not very easily if I'm legally prohibited from doing so! IMO medical ethics is wrongly biased towards preserving life at all costs.
Then he went about begging the question:

> What does having a lot more energy let us do? For starters we can avoid the worst of the climate crisis by aggressively shifting to electrification of transportation, heating and cooling, production and so forth.

Electrification means a decrease in overall energy usage. No increase in energy production required.
I have no idea. Some of my non-technical colleagues seem to love it for gossip, like baby and vacation photos. They also created lots and lots of topic rooms, like 10x our headcount. Inside it's mostly crickets.

I muted email notifications on the first day and then forgot about it :)
recalls me of the time where at office the LCD screens would sometimes turn off, at seemingly random locations. it took a long time for people to realise movement caused it, then further time to discover it was when the chair would pump when they stood up.
I'm watching a lot of football (live and on TV) and this is very normal comment in man's game.
land value is mostly location value. Land value captures all improvements that aren't on the property itself.
I think it is a clear cut, mostly because I do not think that compression compromises any of those features, all while making the user experience better.

For any storage system like this you usually have a few bottlenecks. IO and Network are the obvious ones, followed by tiering (cache, fast io, slow io, ...) and at the very end CPU.

Now let's say network is your bottleneck. If you can send the data to the client in a compressed for then you get the compression ratio as additional bandwidth. And the user would get the data quicker! So compression to the network is a clear win.

But the common bottleneck is often IO, a high end SSDs with 1M IOPS at 4KB would _theoretically_ serve 4GB/s, a 40GBit link. That's without any redundancy over other overhead.

Again compression to the storage layer would decrease the total amount of IOs, thus making sure a customer gets data quicker.

Ok, let's say both are not the issue. The fastest compression algorithms compete with memcopy. So if you need just one copy of your data you might have been faster by compressing it.

Especially fast compression algorithms (zstd, lz4, snappy, lzo, ...) are worth the CPU cost with virtually no downsides. The problem is finding the right sweet spot that reduces the current bottleneck without creating a CPU bottleneck, but zstd offers the greatest flexibility there, too.

Oh for range requests.... Those large objects are likely split anyway, for easier error recovery (imagine 100MB into a 1GB transfer you notice that the file data was corrupted - not good). Once you work on blocks it's easy to do somewhat efficient range requests again.
>And Google is far from the only party that wants, uses and will benefit from HTTP/2 and HTTP/3.

So would it happen if Google wasn't involved?
this point is brought again and again by the late John Holland (check out his books) and by his protege Melanie Mitchel...
Danish and German layouts look quite similar. Interesting that switching the layouts is so common. I guess I'm going to try that and see how well it goes. Thanks!
Super interesting podcast (in general)! Thanks for the links.
Usually, even at zero comments, a story that has been posted the day before is considered a dupe.

That said, I'm happy this time around it got more attention.
“There should be one– and preferably only one –obvious way to do it.“

If you’re not maintaining one of the libraries listed in the article, and try to pull any of this “clever” stuff you’ll be bitten on the ankle by a pythonic snake. No exceptions.
I agree. And even if I didn't, that MIT analogy is very persuasive.

So your advice is to not apply at all, or just not focus on it?
Do you mean the mac experience used to be better? I don’t really know, i have windows. What has degraded?
I see plenty of examples where gender-blind treatment does not appear to be the goal of people.

Some of these are biased against women while others are biased in favor of them.