skysight-inc/HackerNews huggingface dataset:
In regards to the subject I think it is also important for the developers to understand and agree upon what the mainline (master/main/etc.) branch represents. For me it should contain only commits/changes which result in the new HEAD properly working and having a bug fixed and/or feature added.

So the feature/bug/etc. branches can contain multiple commits which are helpful for the developer(s) that's working on it but it all should be squashed into a single one during merging into master.

In short the history noise in master should be kept in check and reduced as much as possible which makes e.g. bisect easier as we don't take into account pointless commits and the history is cleaner. Problem is many think "more is better" and they end up with branches that are much more complicated to work with and reason about.
Easy enough for ChatGPT?

https://news.ycombinator.com/item?id=34738699

> Good idea for a website for portfolio but a good front end person can likely rig it up, I just did a version with asking chatGPT and dropping code into code pen. If there is a market there for you then someone will make a freebie. Than again maybe less tech savvy need weird things like this as they certainly do phone screenshot ones/ templates which could be an electron program or site mod of this

https://codepen.io/gschier/pen/AgLYBE
And for this case, highly highly doubt a threat actor would burn a zero day for a Reddit phish.
Absolutely, I was thinking of things like economic and geographic factors with my parenthesis note.

But some of the commenters seem to be unaware of those constraints and how significant they are, or at least, use a tone that conveys those assumptions.
I put a WD 740 2TB 2230 SSD into mine and it works exactly as before, only with far more space.
Most likely it is fried in animal fats.
Alternatively, you can design your units to be easily repairable so you can stockpile spare parts, and do proper testing to reduce the amount of products that fail in the first place.

The problem is that virtually anonymous sellers and dropshippers on Alibaba and Amazon can and will undercut the pricing that is required to support that kind of infrastructure and development - and I'm not sure what the correct way is to prevent that, while still allowing start-ups and small shops to sell stuff in the EU.

Maybe an idea would be to make exemptions for small scale runs - think of something like a combination of:

- below 1000 units sold in total for a company over all its lineup

- at least the development work of the product must be domestic in origin (i.e. the company must be domiciled in the EU and at least 50% of the development work must be done by that company - that leaves startups free to hire overseas talent, but prohibits dropshipping China crap or production of pre-existing designs)

- handling warranty claims must be done in the EU, with a requirement of "repair first" to incentivize feedback into product development.
I'm not giving reddit my phone number, I get enough junk calls as it is.

Edit: Reads comment by Maxburn, googles TOTP and Authy

Why the heck do I need a 3rd party involved? Ugh
> unqie_ptr have overhead. It need to run its dtor etc

Technically it is correct, it causes an extremly light overhead due to the inability of the compiler to optimise a part of it.

In practice, even in HPC, I never notice it to have an impact ever.

And as an advise for any new C++ programmers: Please JUST use unique_ptr, everywhere, all the time...

Trying to manage the lifetime manually with new/delete in modern C++ is not worth the cost in 99.99% of the case.
If the impact of unique_ptr is noticeable in your program, you are very likely in a realm where you should not even doing memory allocation anyway.
It is very possible my information is out of date or I was using an older version of dot-net. Thank you!
If I attended a social club and my comments from 10 years ago were permanently engraved on the walls, I'd be much less honest and open.
WebAuthn is an UX improvement as well as a security improvement. I sympathize with your point, but in this case it’s easily sellable as the cure to the rest of your list … unless you somehow lose your key.
I've spoken about it generally with my therapists, and don't know many people with PTSD, but know some with CPTSD from a support group.

One person I know who had a "lesser form" of PTSD is a nurse. He worked in Zagreb in the wake of last year's earthquakes in Croatia (the hospitals were an absolute mess due to really unfortunate timing and everything happening at once: earthquakes, harsh winter and no/little heating and electricity, prime-time COVID). I say lesser, because his symptoms (nightmares, hearing sounds that aren't there, disassociating) receded on their own after a while. Maybe it wasn't lesser, but maybe his mind is just more resilient (for an unknown factor).

Yeah, I agree with with you that every PTSD is different (even within the same "subtypes" it's not very consistent).

I believe they're grouped together because of how they (or at least as far as experts know, which is also limited) has some common mechanisms in the brain. And I guess it helps to create a jargon for technical discussions too, even if not perfect.

But yeah I think the topic is too nuanced for layman like us to delve deeper into, since it's... A rabbit hole and a maze with lots of dead ends lol
This looks great. Good call on not making yet another plant based meat.
Lyra Starter Game Source Code Now on GitHub
I think that's just a Wikipedia red herring. I'm not sure the amidated glargine has been marketed.
FWIW gross ridership numbers suggest it was an era of slow decline, until it got privatised and the number of passengers skyrocketed https://commons.m.wikimedia.org/wiki/File:GBR_rail_passenger...
Simple: just declare that the text of the law isn't authoritative, but the meaning should be the guide for judges. Then they get to do whatever they like.

I think we're 15 years into this program in America.
Same here. Clippy and rust compiler made me switch to Rust from c++. Now after experiencing cargo, I find python to be insufferable (tooling, not the language).
> for no clear purpose

performance may have been one driver, though for the "API web" which is the main use case there are better performing options than json

> everything looks like a waste of time overall

maybe all that matters in the end is to be gainfully employed. having multiple formats and standards helps with that. when the Euro got introduced in Europe thousands of FX traders busy trading national currencies had to switch to trading real estate.
You should remove the quotes then
I'm an ordinary human and I disagree. I would not expect a blank line to end the [hosts] table. I find it nice that you can visually separate different categories of entries under a table. I also find it nice that global entries must be at the top of the file – more organized and fewer opportunities for such global entries to get lost.
Enjoyed your article on backups. I was intrigued by the idea of NAS as a solution to bit rot, but when I looked at NAS products, sticker shock dampened my interest. I've been using git-annex so I looked into how it deals with bit rot. It shares the same backup philosophy as git: lots of copies to keep stuff safe.

See https://git-annex.branchable.com/todo/Wishlist__58___Parity_...
Very legit point here. There's a huge ethical but legal too issue when it comes to dataset abuse.
Great, so we agree that it is fair use for OpenAI to train on copyrighted works as long as the person using the model does so in non-infringing ways and that the liability rests with the person using the tool.

Logically, the model must be considered in fair use if we are to allow Supabase Clippy. This is how the courts will see it!
First mainstream fast food restaurant to go back on this being a bad idea and offering “non vegetarian fries” is going to financially obliterate restaurants chasing the vegan meme.

Once you’ve tasted what you’ve been missing with tallow and dripping fries the rest taste like trash.
Maybe. The concept of derivative works seems to be the one that keeps popping up in these kind of AI discussions.
This article (https://www.nbcdfw.com/news/national-international/chick-fil...) says it is because they include milk and eggs, which doesn't make sense, because while vegans avoid those, vegetarians eat milk and eggs. However, the article also says they don't have any designated area for prep, so your cauliflower may touch chicken or may share a fryer with chicken.
Not entirely true. You can pool allocate a C++ coro.
It has eggs in the recipe. It is mentioned here:

https://www.usatoday.com/story/money/food/2023/02/09/chick-f...
> honestly responding rather than saying something unrelated

Unrelated? I responded to your claims, point by point. You said "tiny, inefficient and use highly enriched uranium", more expensive than Vogtle, China slowing down their nuclear program, and civilian reactors being used for breedign Plutonium, after which they fizzle out.

I dedicated a paragraph to each of these. Feel free and re-read my response, and try to link each paragraph with your corresponding claim.

Also, feel free to familiarize yourself with this site's guidelines. The link is at the bottom of the screen to the left of the FAQ link, but here it is for your convenience:

https://news.ycombinator.com/newsguidelines.html
Why do people advocate for JSON so much? It's simple, I can see that, but it also got most of its stuff wrong. If I had a liberty to choose a format in which I want to receive data, JSON would've been very much down on the list.

These are just the problems that actually bit me in my professional use of JSON, not some theoretical possibilities:

* No bounds on how big integers may be, subsequently, an ambiguity about what to do if the number is bigger than what would be considered a typical integer size for the platform: should it be interpreted as a float or as an integer? In my case, I had ids coming from a database that used 128-bit to represent them and the client side silently converted them to floats, but, on the way back, converted them to integers again, which resulted in rare collisions and lost data.

* No defined semantics for repeated keys in hash-tables. I used a library that tried to stream JSON in SAS-like way, but the authors didn't realize that duplicate keys are a possibility. Again, this caused subtle and hard to identify data integrity issues.

* Unnecessary null value. For some languages null and false are the same thing (and I prefer it that way too), but converting data back and forth between JSON and language-native data would sometimes produce inconsistent results, and, again, caused a once-in-a-year case of data integrity issue.

* Mandatory Unicode string encoding. Caused problems with DICOMs from East Asia. DICOMs have some special encodings that can have characters not representable in Unicode. You can guess that I've learned it the hard way too. And there isn't a way to transfer raw data (of course, you can Base64 encode it etc. but that's not a function of the format, the parties need to agree on format extension in order to understand that).
not to mention that future versions of yourself would think that past versions surely had mental bugs :-)
"Quiet quitting", as you so aptly did not wish to call it, does not exist in a vacuum; it is a response to unheard, unaddressed critiques from the people who actually do the work, and likely the only avenue those workers have left to 'voice' those critiques. I think anyone who has worked in a large org, especially hot on the heels of laying off so-called 'high performing' employees, should be able to empathize with the message.
depending on the artist some fans might not enjoy being short changed if the drop in quality is perceivable.
Agree on your last point o some degree (transit) but many cities’ downtowns are struggling post (“post”) pandemic. It’s a bit of a laff to lay this at the feet of progressive policing and NIMBYism, which seem like issues you have at the ready to apply to whatever negative situation.
Switzerland, for example. There will be no Steam Deck in Switzerland before at least 2024. :(
That's usually not a problem though.

The software can look at $XDG_WHATEVER/tool/config first and ~/.toolrc second. Everyone who wants the clutter can keep using that.
This case is probably pretty relevant right now - and this is with an impersonator and the right to use the song: https://www.theguardian.com/music/2023/jan/27/yung-gravy-sue...
XML is nowhere near "hip" these days, but I think it is underrated. Yes, a lot of bad things have been done with XML, but the technology itself is just fine and sometimes hated for the wrong reasons.

XML is considered overly verbose, which is not always the fault of XML, but of how it is used.

<dependency>
<groupId>org.junit.jupiter</groupId>
<artifactId>junit-jupiter-engine</artifactId>
<version>5.9.2</version>
</dependency>

Could (in principle) be written as:

<dependency groupId="org.junit.jupiter" artifactId="junit-jupiter-engine" version="5.9.2" />

What really stands out is XML Schema. It is so much more powerful and precise compared to Json Schema.

See also: http://www.nichesoftware.co.nz/2017/04/25/in-defense-of-xml....
Yeah, sadly it is. With e.g. Elixir I can literally get into a REPL and prototype my solution in minutes, right there on the spot, and then just copy a few lines from it and have the solution be 90% done (minus tests, of course).

With Go and Rust I have to make a dedicated function somewhere and then have it be called after starting the program. Ain't exactly rocket science but the difference in time to do it and the convenience is still very stark.

I love working with Rust for the stability and speed it gives me but the value proposition and daily coding flow are VERY different compared to a dynamic language. With Elixir I am mostly just brain-dumping and stuff happens extremely quickly and fluidly, with Rust I kind of sigh and accept that the next 10 minutes I'll just be writing and writing. Might even zone out and make a dumb mistake because I have to spend more keystrokes and more time to do something I'll do in a minute in Elixir.

Maybe it's time to look for snippets support in my editor. Or start asking ChatGPT for them.
That's a good point about gmail, but I was thinking of outlook, apple mail, the gnome mail client, and this one called mimestream that I use now. They all have that same familiar 3 column layout: mailboxes, list of messages, message contents. That layout has been the norm for a while, so I think calling it trendy is a bit of a stretch.
JSON:

"path\to\file"

XML:

<a>path\to\file</a>
Palloc: DRAM Bank-Aware Memory Allocator [pdf]
I was really mainly responding to the point of JPEG aiming for indistinguishable. Point being that for a lot of purposes we're fine with, and might even be happier with, very different tradeoffs than those JPEG makes.

Going specifically to AI, we do agree that the lack of constraint means they're not compressors in and of themselves. The training compresses information, but that does not make them compressors. Learning and compressing information is, however, at least in some respects very similar. A key part of the LZW family of compression, for example, is applying heuristics to build a dictionary of bit streams (terms) learned from the input.

AI models can potentially eventually be used at the base of a compression because the models encode a lot of information that can potentially be referenced in space-efficient ways.

E.g. if I have a picture of a sunset, and can find a way of getting Stable Diffusion or similar to generate an image of a sunset that is similar enough from a description smaller than the output image, then I have a compressor and decompressor.

Ignoring the runtime cost and that bringing that down to levels where it'd actually produce a benefit, depending on how close the output it, it may be a totally useless algorithm leading to images that are way too far from the input, or it might turn out pretty good. But the tradeoffs would also be very different from JPEG. For some uses I might be happy with a quite different-looking sunset as long as it's "close enough" and high quality even at very high compression ratios. E.g. "A sunset over the horizon. Photo taken from a beach. A fishing boat in the water" fed to [1] produced a pretty nice sunset. Couple that with a seed to make it deterministic, and I might be happy with that as a compression of an image of a quite different sunset. For other uses I'd much prefer JPEG artefacts and something that is clearly the same sunset. For "real" use of it for compression you'd want someone to research ways of guiding it to produce something much closer to the input (maybe heavily downscaling the original image and using that as the starting point coupled with a description; maybe a set of steps including instructions for infilling etc). I think finding the limits of what you can achieve with trying to use these models to reproduce a specific input with the most minimal possible input would make for fascinating research.

[1] https://huggingface.co/stabilityai/stable-diffusion-2?text=A...
I don't believe they stopped USDC withdrawals, just actual USD
Users rarely submit stories they've written, tho. "Self promotion" tends to work poorly here. Perhaps this study should look at comments, instead?
Yes but the server came into contact with 500 people that day, for minimum wage. We came into contact with just one, got a cup of coffee out of it and then went to WFH on tech money.
The implications would be checking if it is null before performing the deallocation of the memory, which is a runtime overhead.

Stack overflow says "delete" would check for null before deallocation: https://stackoverflow.com/questions/4190703/is-it-safe-to-de...

Happy to be educated
You know, I used to think the same thing. But then lastpass got hacked and it made me realize password managers have a lot of eggs in those baskets. It might be worth using two separate password managers and keep TOTP in the second one.
Early Adopter Program: AI data analytics tool. ChatGPT instead of SQL
> You need more discipline (like make sure that you run test and linters locally)

That sounds error prone. Wouldn't it make more sense to have an automated system to run tests and linters for you...?

> but my experience is that makes the whole process easier.

Sounds like you would just have people breaking `master` constantly to me. And how do you do code review? Or don't you?

> there is nothing continuous to coding on your branch and merging after a few days.

Yeah I guess the meaning has changed a little (or maybe standards have changed). These days CI basically means automatically testing every commit.
>Fun fact: Apple still doesn't provide two years of warranty in the EU, unless you PAY for it via an Apple Care extension.

They do provide it. In fact, they cannot by law NOT provide it.

What they don't provide is their special "Apple warranty" that covers more stuff than the standard legal guarantee against a falty good.

But you automatically get (and they comply, as they must) a standard EU guarantee if the product has production issues etc.
2023 State of Databases for Serverless and Edge
It's a mobile friendly UI, that's one way this website stands out above many others.

Sure, it looks like the underlying process is a perspective shift, a gradient, and a blur, but making the UI usable deserves some credit.

If you don't feel like paying, you can repeat the process in any free image editor for a fraction of the cost.

Perhaps the value add will be bigger if the service gets expanded, for example when it also works with videos and allows for transitions. You can throw together a product demo video a lot quicker by combining that with some captions. It won't be much, but in many areas, it may just be enough to stand out in the crowd.

If I needed one of those "camera panning across a rotated screenshot" videos for a product, I wouldn't know where to begin. Maybe automate imagemagick? Teach myself Blender? I imagine for many tech illiterates (and there are a lot of those, especially these days) will have the same problem with plain images.
> How is Netflix so blind to this? They think they will gain those recipients of shared accounts, but in reality they're losing the ones who are actually paying for it.

I would guess they see it as a numbers game. Enforcing sharing restrictions more aggressively will cost them some customers who rely on it, and gain them some (maybe only a minority) who currently freeload. What will the overall result be? I don't know. I would have expected them to model various scenarios though and decide there was enough potential to make it worth trying.
And the nice thing about those NAME="value" pairs is you can now source it directly in shells, or read it with some straight forward, usually built in library in many programming languages and supporting tools
> since C++11 there is no reason for not using smart pointers.

Smart pointers lure you into a dark alley where each tiny object lives in its own tiny heap allocation, and before you know it you have so much memory management sprinkled decentralized all over your code base that the memory management overhead becomes a performance problem, but at the same time it's too late to do anything about it because it would mean rewriting everything (this is then usually when the desperate search for a silver bullet like a "high performance memory allocator" starts).

(not that Rust is necessarily better in that regard when people start to work around borrow checker restrictions with Box and Rc...)
My Strange Day with Bing’s New AI Chatbot
Cample.js: Reactivity without virtual DOM
If not vegan, then what?
Not a UX improvement. Most users need a yubikey for the computer unless they have a new Mac. Asking my 65 year old dad to keep up with a yubikey is not just bad UX, it's failing UX. It simply will not happen.

I don't even think it's realistic to get him to use a smartphone for this, he hates the things.

WebAuthn works great for your Web 3.0 startup but as soon as you're talking about the average user, who is likely decades older than the commenters here, and far less interested in keeping up with these things, and far less patient with the hassles... asking them to carry hardware is a nonstarter for so many.
>This was basically impossible to do in the early personal computer era, before memory protection was a thing. So MacOS, Windows pre-NT, AmigaOS etc were all built around the assumption of applications reading each other's memory.

Very true. The user had a different option for that, since DOS was basically a program loader, and only one thing ran at a time, they could boot into program A, and use it with disks Q,R,S and know that no other disks could be corrupted. Then later, boot into program B, for disks X,Y,Z. It was capability based security, where each diskette was a capability. (Before hard drives ruined that trust model)
Is Apple letting another AI opportunity slip away? – Macworld
> were useless to begin with

Or useless with office politics, and didn’t manage to market themselves well with the new lead. It’s never been clean-cut in my experience.
> 2 years is of course a very long time

How is 2 years a very long time for an electronic device? Most larger electronics (washing machines, dishwashers, fridges,...) have a 5 year warranty by default here, also many cars do.
There are settings you can place in .gdbinit to avoid stepping in to internals of anything you don’t want to step into, be it std library classes/functions or your own code.

Much nicer than hacky ifdefs.
It actually doesn’t seem to qualify as an electromechanical pinball machine at all. Given the 17 computers in control and modern playfield mechanisms and sensors, it is almost certainly considered a solid state pinball machine.

EM machines use much older tech - look at Gottlieb machines from the 40s-70s. Even they switched to SS by the end of the 70s