skysight-inc/HackerNews huggingface dataset:
Use MySQL if you're expecting to have to do large operational database tasks re: migrations, maintenances, with no ability to go offline. gh-ost, percona-osc, the new INSTANT DDL stuff, is all quite far ahead in MySQL-land. Additionally, Vitess and Planetscale are making huge strides in MySQL performance. There are more people and guides in the world to help recover even the most mutilated of MySQL databases. MySQL gets more love in extremely large enterprise-level organizations, and it shows.

Use Postgres if you need some of the quite-good extensions, most notably PostGIS, or if you just want things to work; most documentation will be postgres flavored. Postgres gets more love from web-developers, and it shows.
Why is it intellectually bankrupt? The IQ test was specifically designed to test for a _lack_ of intelligence, having a 160 IQ doesn't really mean much as the test wasn't setup to measure above average intelligence.
pick the database that you are most familiar with
Postgres has a worse implementation of MVCC. It results in more bloat being produced, and slightly slower updates in a highly concurrent environment. Most businesses don't operate at the scale where this matters. But on the flip side, the tooling and developer experience is much better.
Er...did you read that?

> People interested in moving to Mars could pay for their flight with a loan. Once there, people would be able to pay off the loan by working in anything from iron foundries to pizzerias.

Indentured servitude.

> This city would be free to govern itself on its own terms, as indicated by the Starlink internet service terms and conditions released in October 2020. This appears to stand in contradiction to the 1967 Outer Space Treaty, which states that the launch origin country is responsible for subsequent space activities.

Avoiding all current human laws.
> Min wage. changes the supply, not demand.

If you raise the price of something–anything–it lowers demand. That's why minimum wage laws create unemployment.

> It may or may not yield less employment depending on elasticity.

If you're earning your employer $10/h and the minimum wage rises to $11, you will not have a job. Either right away if the employer realizes it, or eventually when they go out of business if they don't.

Adding elasticity to the equation unnecessarily complicates this. Some things have elastic demand, others have inelastic demand. Why focus only on the relevant case for the point you're making? The overall effect of a price increase is decreased demand.

> If businesses are flush with profits, then they'll eat the higher labour input and that's it

Profits have nothing to do with it. If a business has employees at some wage and the minimum wage rises above that wage, they will, at least eventually, replace the low-wage employees with new ones (or with automation) that add at least as much value as they are paid (or cost). Profits don't magically make businesses waste money on inexperienced employees where they could otherwise be more efficient with more experienced employees at the same price or with automation.

> Otherwise, prices may rise

Not without an associated drop in demand.

> You can see this more acutely in healthcare, where there are stronger regs, because the power asymmetry is bigger aka the supplier has the power of 'life or death' over the customer.

Assuming you are talking about the US, there is no difference there. The supplier has power because they are able to limit the supply, e.g. the AMA limiting (with govt help) the number of doctors who graduate every year. https://blog.petrieflom.law.harvard.edu/2022/03/15/ama-scope...
Yinzer!
> "Mojo Financial: We are a company and need to make money, but will do so based on products. We aren't sharing all the details on that right now, but you can follow our web page and newsletters etc for updates. We'll open things up progressively over time as it matures."

> "Opening the MLIR design docs: Our hands are pretty full at this point, and I don't think the general ML community would care much."

> "GPU numbers are not far away, and benefit directly from everything we've shown so far. You'll need to use your imagination or extrapolate or imagine until we publish our next step."

> "Modular Inference Engine: Implementation details: We haven't shared much about how our inference engine works internally yet."

This is great! This is great stuff. I get the feeling they are trying to build the 'MATLAB (in terms of closedness) for AI' and 'extend and extinguish' the Python codes.
This is the correct answer.

Whichever one you start out with, you will be annoyed if you switch to the other one 5 years later. I started out with mysql, and when I started working on a postgres project, I was shocked at some of the ways it was lacking (how am I supposed to store email addresses in a database without collations?).

But when postgres folks grouse about stuff in mysql, I'm usually nodding along and saying "yeah, that would be nice".

They're both great options. If anybody on your team is already an expert at one of them, use that one.
Is the target audience for teenage engineering products people that like extremely sleekly designed products that also have nice features; or do people in their industry hold them as highly regarded products that have unique features and perform well beyond their sleek design?

I'm asking without judgement and out of ignorance of the field of audio engineering. I absolutely believe that there is a market for sleekly designed products that also happen to function well; but I don't know if audio engineers (and other people this targets) also believe that teenage engineer products are worth the price beyond that.
True, I have a photograph taken in Kenya that has been variously described as in California, Guatemala, Colombia, Australia and South Africa.
A few reasons:

- Transactional DDL statements (schema modifications)

- Better support for UPSERT operations

- Better JSON support (including ability to index into JSON columns)

- the RETURNING statement to return data that was inserted/updated

In general Postgres is a lot more featureful than MySQL.
You have working hours and you have non-working hours. I don't see the upside in punishing yourself for not working during non-working hours. Those hours are for you. The proper way to look at this is 'be productive during the time you've allotted.'
create table strict
I work on infrastructure for serving large language models but I don't have any background in ML, so my perspective is looking at these models as a black box (and also conversations with the people that do the ML stuff). It is the case in practice at least from a latency side that with a fixed context length N, embedding any number of tokens from 0 to N takes the same amount of time. Perhaps it's a difference between the conceptual and actual implementation on GPU?

edit - This occurred to me after the fact but I wonder if the difference is that the use case I work with is processing batches of many different embedding requests (but computed in one batch), therefore it has to process `min(longest embedding, N)` tokens so any individual request in theory has no difference. This would also be the case for Anthropic however.
Postgres doesn't have type hints and it might create a false impression of robustness until it messes up table statistics and does FULL SCAN against a table with millions of rows ignoring all indicies. It happens super rarely though, so if you run anything critical, you'll probably be down only for a few hours once a year or two. Be ready for this to happen though.

Apart from that (and noticeably higher memory consumption), Postgres is most likely preferable.
Curious what this will mean for the vector db vendors. Imagine finetuning would be quick and cheap. Could there be a world where vector dbs aren’t needed anymore?
Postgres for anything with a single database size < 4TB.

But if you need something that can handle 100TB+, go Vitess(mysql compatible).
Masayoshi Son should really be a mod in r/wallstreetbets
It's not "loss". The money of SBV (Saudis?) has changed hands and now belongs to whatever startups or funds they had invested in.
LLMs can do that without any examples (zero shot) or with one or a few demonstrations in the prompt, if you can describe the task in the limited context window.

If you want for example to train the model to learn to use a very large API, or access the knowledge in a whole book, it might need fine-tuning.
The Postgres query optimizer is more powerful than the MySQL query optimizers [1]. It generally scales better for OLTP. Also tons of extensions that can accelerate your workload.

[1] - https://ieeexplore.ieee.org/document/9537400
A lot of people seem to imagine layoffs happening (or that they should happen) according to some well-calibrated stack ranking at the company level. But that's not typical at all.

Sure some employees on PIPs or otherwise considered low performance may be cut regardless of role. But more typically projects get cut/defunded (whether in engineering or elsewhere) and those roles are eliminated or cut back. A good performer may have an opportunity to find a job elsewhere in the company but, in my experience, that's pretty hard given that any open slots were probably also closed as part of the layoff and everyone is pretty distracted anyway.
Ultra sleek design.
Does anyone have any idea how consuming this "Vitamin D enriched mushroom" can be compared to taking a vitamin D supplement? Are they absorbed by the body in the same way? Also wondering compared to just being out in the sunlight yourself
The US median wealth and income (PPP adjusted) is at or near the top. The 75th percentile is significantly higher than all other countries because educated knowledge workers are building products that are used by the entire world.
Yes, government spending needs to be cut -- but isn't the time to fight for fiscal responsibility when you're writing the budget, the tax code, and the various bills which authorize spending? Causing a crisis by defaulting _after_ you've overspent is only going to make lives more difficult for the general public.

Want a line in the sand? Promise to vote not to reelect your representative if they vote for a budget which increases spending at faster than k%/yr. If you're a hawk, pick k to be negative. But this default mess is just dysfunctional.
Right, the vast majority of places where you can order a non-Uber taxi are no more regulated than any other job. There was no "Evil medallion cartel", that was always just propaganda that Uber explicitly paid for.
I'm already spending time with my wife. I didn't create that list in a particular order. We have a quite supportive relationship and I'm quite thankful for it. Maybe I might have sounded over-depressed in the article.
There's nothing wrong with inheritance, even in JavaScript.
Wow thanks for showing me about `openssl s_client`. I just have this a try and you're it was quite easy!

openssl s_client -connect example.org:443
[TLS details...]
GET / HTTP/1.1
Host: www.example.org
<newline>
<newline>
[headers and HTML response!]

The one thing tricker nowadays is almost all of the time you need to send the `Host:` header for things to work. Took me a sec to realize that since in 1998 it was almost never necessary.
This one: https://puri.sm/products/librem-5.
> What sort of functional requirements would cause you to choose one over the other?

Simple: I don't like having headaches. Therefore, I chose postgres.
I am not from the US and I didn't downvote, but my understanding is that your congress needs to approve spending twice: first they vote for laws that require a budget to implement, and then later when the money is actually needed (but isn't actually available without exceeding the debt ceiling) then they need to vote again to increase the debt ceiling.

Trying to keep spending under control at that second stage, is like managing your budget by refusing to pay your credit card bill. It would make much more sense to control spending at the first stage.
Again, I don't still know if this is the case, but you could use smaller instances with MySQL aurora than with Postgres, given the way our application worked it would have made a big difference for us if we had used mysql.

RDS/Aurora was our most expensive resource so we were looking at ways to cut that cost down and mysql was one option (though the way the app worked and the extensions that it relied on made it not a possibility.)
i worked for a company once with a large (10’ sided cube) and very high-quality anechoic chamber and would go in there on lunch breaks to mediate, was fantastic. (never had audio hallucinations.) i was young and had no hearing issues which probably helped.
> burning fuel is as efficient as it gets

Considering this is false as many commenters have mentioned, do you feel any obligation to edit or delete your comment?
Going out on a limb here, but I would guess it doesn't. If the pricing will be similar to the other entry in the field lineup (TX-6) we're looking at many multiples of the price of a Zoom H4n Pro, which I also would guess has a wider arrange of features - except the transcription.

That being said - teenage engineering is probably not looking to compete with Zoom. The branding is totally different. TE is looking for a premium market, while the first thing I was met with on zooms homepage was a button that said "New lower price!".

Teenage engineering continues doing something that I don't really understand - making me want to buy stuff that is really expensive that I have no need for. I won't buy these things, but every time I see them I do appreciate the craft.
It makes a big difference, but even if you removed 90% of the fresh mushroom's weight without changing vitamin D levels, you'd still only have 1000 IU / 100 grams.
you put a cleanup label at the end and in case of any error set the return code and jump there, where all the buffers get freed.

Otherwise you have to free all the buffers in every place where an error might happen, and you will most likely forget to free some or double-free.
$80 tape dispenser? Shut up and take my money!
Here are some guesses at popular CEOs.

LAWYERS - needs walls of text

Jeff Bezos is known for his long-term thinking and his annual letters to shareholders are famous for their extensive detail and length.

Mark Zuckerberg is known for his long-term vision and often communicates his ideas in lengthy blog posts and public statements.

ACCOUNTANTS - needs numbers, spreadsheets

Sundar Pichai has an engineering background and tends to rely on data and analysis in decision-making.

Satya Nadella has an engineering background and has emphasized the importance of data-driven decision-making at Microsoft.

Warren Buffett is famous for his value investing approach, which emphasizes analyzing financial statements and data to identify undervalued companies.

ARCHITECTS - needs diagrams, visuals

Tim Cook is known for his attention to design and user experience, and Apple's keynotes and product launches often feature detailed visuals and product demonstrations.

Elon Musk frequently communicates his ideas through visually compelling presentations, and is known for his ambitious plans for space exploration and sustainable energy.

ACTORS - needs a conversation, verbal

Mark Cuban is known for his outgoing and talkative personality. He often engages in conversations with fans and customers on social media and in public appearances, and is very comfortable in front of the camera.

Richard Branson is known for his flamboyant and charismatic personality. He often appears in public events and media interviews, and is known for his storytelling and ability to captivate audiences with his words.
It’s a crypto issue. You can figure that out by restating their advertising/business model using ‘cash’ instead of crypto, and asking yourself how long they could go before getting shut down.

Hint: they likely could never have even gotten to the point of taking customer deposits, or would have been shut down within weeks or months at most by regulators.
Sure, I agree with you. Let’s make the tax system somewhat more progressive and simpler. But that alone won’t help enough.

The issue is the spending associated with and related to the “inflation reduction act”. Spending of this type is mostly unnecessary pork.
Yes that too. It also has some of the best quality companies which accounts for a lot of it, but even then it is still pretty extreme.
> It's not obvious to me that fern branches are 'anatomically variable and non-iterating bifurcations', rather than a recursive process that bottoms out at a size boundary.

But hardly any (no?) real-life phenomena are the latter! As a mathematician, I'm as bothered by imprecise use of mathematical terminology as anyone, but, if we're going to call anything in real life a fractal, then it surely means something more like "appears to contain structure at multiple scales" than "the same structure at all scales". As @throwbadubadu points out (https://news.ycombinator.com/item?id=35903049), the classical example of a coast-line will also have different structure at small scales and at large ones, so either we throw out calling that a fractal (OK with me!), or we accept that we're using precise language imprecisely.
The only argument I have would be the soldering irons. You really want a Metcal or Thermaltronics station. They're just so much better that it's ridiculous.

Yes, they are expensive. However, you will have them forever. And you will never have to worry about too much heat, too little heat, or calibration ever again.

Your soldering will be so dramatically better that you will wonder how you ever did without them.
I think that the only reasons to choose MySQL (or Maria) over Postgres for a new project are operational. Postgres is probably the better database in almost all respects, but major version upgrades are much much more of a pain on Postgres than on almost any other system I have ever used. That being said, I would choose Postgres pretty much every time for a new project. The only reason I would use Maria or MySQL would be if I thought I later would want to have something like Vitess, for which I think there isn't really an equivalent for Postgres.
Considered harmful considered harmfuls considered harmful!
Yeah, I know about that, and I'm doing that on all my tables these days. It's just sad that the default behaviour is to allow garbage data, and that if you ever forget to put 'strict' on your tables you'll have a perfectly functional application with no sign that anything is wrong until you suddenly find corrupt data in your database.
My own reasons for blogging:

- Know what I think. Writing it down makes me think a lot more about it.

- Share what I have learnt. It's nice if something I know becomes useful for somebody else.

- Venting. From time to time there are things that annoy me, or ways of working that I don’t like. Then I can write a blog post and argue how things should be instead.

- To learn. Often comments on the posts, or discussions here or at Reddit add to my understanding.

- To better remember. Reviewing a book or a course helps me remember a lot more of the content.

- The thrill of having readers

- Visibility. If people google me, hopefully the top result is my blog.

- As an archive. I can send people links to my blog if we discuss something I have written about in the past.

https://henrikwarne.com/2017/11/26/6-years-of-thoughts-on-pr...
Agreed on feature naming - will fix!

Also I definitely understand your perspective and it makes sense. SuperTokens still is 100% open source - but you are right, as we evolve into a paid offering, there is scope for improvement
Ah, I've had this idea for 5+ years now and just haven't had time to try to build a MVP. Before this year it would have been harder to do well - involve human writers and sentiment analysis. But lately I have been thinking about trying to do it with GPT.

I genuinely think there is a huge underserved market for a "world's most boring news and weather site". Almost everybody I talk to on all sides of the aisle recognizes that clickbait news is one root cause of lots of problems and want an alternative. In fact, in some ways, Hacker News is that site for me.

That said, I don't get why an app not a mobile-responsive website.
They don't have much of an argument, a lot of their material is full of doublespeak narratives, and watered down information. Characteristics which any computer will fail at utilizing properly.
Not sure what language you were coding in but I remember actively hating it 5-10 years ago and definitely didn't think "it's actually good now". It was always getting better of course, but even these days there's lots of problems that would prevent me from saying "it's actually good now".

The Web APIs are pretty lacking:

* WebUSB has only been available for a couple of years

* WebGPU is only now becoming a thing despite the aborted attempt that was WebGL

* Raw TCP/UDP sockets are still experimental

* WASM is still struggling to solve the scaling challenges to make it possible to make available a large portion of existing software as libraries for JS to interop with without overhead.

* WebCrypto doesn't have streaming hash support & fails to standardize protocols that are relatively popular (e.g. ED25519)

From a language level, there's all sorts of footguns/edges that can't be fixed due to back compat and the language is both slow in adopting good features but also fast to adopt features that don't work too well or just plain annoyances when switching between langauges (e.g. did any/all really have to be unique and called some/every?).

The ecosystem also has large annoying challenges with TypeScript being super slow to type check even small projects, a mess of bundlers to pick from (most of which are ass slow except for ESBuild and maybe SWC), linters (only really ESLint in the game which is slow for TS), formatters (prettier which is slow but thankfully there's now dprint), ES/CJS bifurcation that's a nightmare to manage, tooling that only works with very specific combinations of things, etc etc etc.

You can usually build something passably if you know what you're doing but it's a mess for someone new entering the field and even after having spent some time in it I'm finding myself futzing with project settings quite a bit to accomplish some slightly off the beaten path combination of tools.
Can it be formulated as a bunch of koans? I don't trust things that aren't.
I'm not convinced that putting a real head-scratcher as the very first choice in a tutorial mode is a brilliant move at all. Tutorials are supposed to be easy and hand-holding.

But also: this isn't actually a hard judgment call. It's just bad instructions. There's an objective difference between "content that breaks laws" and "content that promotes the breaking of laws" and the rules could easily be changed to indicate the one they want.

If you were playing a platformer tutorial and you came to a gap and the tutorial instructions said "Press A to jump over the gap" and then when you tried you fell in and died and the tutorial then said "That was too big a gap to jump over. You should have pressed [Down] to climb over it instead", would you think "Ah, what a brilliant meditation on trusting trust and how the right choice is not obvious" or would you think "this is a shitty tutorial for a dumb game"? I'm not saying there's for sure a right answer here. I could imagine a well-made game where the tutorial straight-up lies to you and gives you the wrong directions. But most games like that are just badly written and poorly thought out.
Chatbot Arena Leaderboard Updates