skysight-inc/HackerNews huggingface dataset:
news agencies may well be full of real normal people with interests roughly aligned with the common man, but they're owned by strange rich people with interests usually completely at odds with those of the common man. the issue isn't one of accuracy or inaccuracy, or a failure of a valid attempt, it's one varying degrees of success at attempts to do something other than honestly tell you what's happening in the world.

all news agencies larger than a certain size should either be non-profit or publicly-owned
“AI”, and the trouble with inaccessible SaaS
> I think the bigger issue is how our economic model is so reliant on maximum acceleration of adoption that we never stop and ask if people are fine with the jobs they have

This was never and wont ever be the point of a job though. Its what the market demands, not what people want out of a job.
That's what my post is suggesting. The tricky part is making sure you don't sneak a !Leak type from 2024 code into some 2021 code.
Yeah, that's why sqlite was adopted for this back then - many devices still used FAT32 on the storage volumes where tiles we often stored/cached and that had horrendous small file performance - a plain white 130 Byte PNG tile could result in 64 kB being used.
Sorry I don't know about courses but I do have an idea.

Go to Upwork and search for Vue or Vue.js or other relevant keywords and try to find a project with something like a specification or at least a description of the system.

Then pretend you were hired for that project and build it with your stack. You can then put it on a portfolio site.

You might also be able to do something similar with other jobs sites, job postings, or just looking at some interesting SaaS or other software and trying to build it in your stack.

Just make sure to find something interesting and not very complex.

Break off little pieces of it and build up your experience day by day. It is quite a lot of technology to become familiar with. Don't be disappointed if you can't remember. Be patient with yourself. It's a huge amount of information.

Get a $20/month ChatGPT Plus subscription. You can ask it to create exercises or a curriculum. The biggest issue will be training yourself to use it judiciously so you actually learn how to use those technologies rather than learning how to just prompt ChatGPT. I guess it could backfire so you may have to consider blocking yourself from opening ChatGPT entirely if you really can't stop yourself. Unless you want to take the chance of not being able to program with those technologies at all without ChatGPT.
Is StackOverflow slow? Maybe. Has this ever bothered me as a user? Nope.
I guess the XS Max would be well outside of AppleCare+ territory, but for those of us who upgrade every 2-3 years, AppleCare+ is great.

It's literally insurance for your phone except you don't have to deal with the insurer.

I've only used the Express Replacement Service part of it twice, but when I've used it, it's been like magic. I get a brand new (refurb probably, but who can tell) phone within 2 days, and then I send back the old one.

No questions asked, no weeks of wrangling with the insurer.
>For good, functionality-related reasons at the time

Having it work surely is better than those drawbacks. Things can be improved and iterated on over time.

Wayland adoption was damaged by this.

>and everyone in the Wayland space had been using the mesa library

They chose to make themselves compatible with a single graphics driver. GBM ended up having to be rearchitected so that Nvidia could create a backend for end.
Unity has an svg package which has been stuck in experimental state for years like many other unity features. I wouldn't call it true vector graphic engine. It can be configured to either generate bitmap sprite at build time (minor convenience over converting svg to bitmap manually) or it can generate triangle mesh (from what I understand also done at build time). In the second case once you start zooming it doesn't necessarily look very great either. Once you zoom out lines look bad since they are formed by thin strip of triangles which doesn't work too good for few pixel thin lines . And when you zoom in you start to see that its made from triangles instead of round curves since the generated triangle mesh is fixed. With both approaches svg benefits are largely lost compared to true vector graphic rendering engines.

I haven't seen any true 2d vector graphic engine suitable for games after flash beside the software made to be alternative flash players. Yes there are a bunch of games that still use that art style but in many cases they might be drawn as vector graphics, but then converted to bitmap for the game engine, maybe with some runtime shaders on top for sharper look.
SVG is just way too different from how game graphic APIs works. Just making a non real time SVG renderer is hard enough already. Even programs like Inkscape whose only task is drawing and manipulating are sometimes struggling with it. Open a more complex SVG and zoom in/out move around and you will see as Inkscape tries to keep up updating and caching the rendered image in chunks.

It might be possible to do something using browser svg support although I am not how good the performance would be with the kind of dynamic content games need.

There are also a couple of UI frameworks which support SVG. For something like that it can be acceptable to use slower but higher quality svg renderer and then caching result. For the most part UI elements are either static or at most move around due to scroll views and zoom rarely changing so caching works very well.
Just a small correction, PS1 had a 2x CD drive (but still supported 1x speeds of course)[1], but the point still stands.

[1]: https://www.psdevwiki.com/ps1/index.php/CD_drive
Imagine an elevator that moves up and down its shaft with a sinusoidal elevation over time. Riding in that elevator, one could detect frequencies with quite long wavelengths compared to the size of a person.

A less abstract example is a boat at sea.
It’s also a bit of a bother if Audacity crashes (or is otherwise terminated abnormally), as the cleanup just doesn’t happen at all then, whereas in the past the recovery process would mention the presence of orphaned blocks and allow you to choose to keep or delete them. But when I had a several-gigabyte project that should have only been a couple of hundred megabytes, and needed to save disk space, I finally found a solution suitable for my simple single-track stuff: Mix and Render. Doesn’t change the audio, but allowed it to clean up the detritus on save and exit. But all up, this is clearly an application-level problem, not something inherent to SQLite.

Hmm… I think I vaguely recall that Audacity 2 had the concept of a temporary working space, whereas it seems that Audacity 3 just uses the .aup3 file as its working space? Some advantages, some disadvantages.

Mildly less on-topic: I looked into Audacity 3’s format, and was utterly baffled by what they’ve done with the project data (what used to be the .aup file). They still encode it as XML, storing it in a single-row table, but instead of just writing it as text, they use a simplistic dictionary coder on it. Just… why? Why did someone go to all the trouble of writing that code? It makes interoperability and inspection much harder, surely harms performance (even if by a trivial amount), and the space saving will be rounding error in every plausible case (like, maybe as much as a few kilobytes out of hundreds of megabytes of audio files).
That is nice. That is why I don't use 'I don't care about cookies'. I do care, I want to press reject, if for nothing else than to send a signal.
I’ll start using it as soon as I wake up in the morning, and while I do not talk on the phone much, I am constantly using messaging apps, a brokerage app, and reading webpages for many hours throughout the day.

I do a full charge every two or three days.
How is design docs different from technical docs?
>> Little's law assumptions:

>> All measurement units are consistent.

>> Conservation of flow, meaning the average arrival rate equals the average departure rate.

Yeah, that checks out as the first and only two parameters most modern customer service behemoths are concerned about...

Reading this whole thing, my mind goes to how to wring optimal customer loyalty from a given queue, or how to relieve a queue in the way that would keep the most customers loyal. I guess that's why you shouldn't outsource.

Arguably, the theory of queues goes a long way toward explaining why the angriest people in a line are also the least coherent. It's funny to think about, in a Rowan Atkinson sort of way, that the more apoplectic you become while waiting the further you go back in the line. hah.
Yes but the national aquarium in Baltimore has puffins and that's good enough claim for me.
> Yes it should replicate the functionality user expects

Do users really expect this now a days? Most users use cloud apps, and almost all of those save after every operation automatically.
In this scenario, R sends packets to S over IPv4 only. So S must have an IPv4 address? If S has an address that is larger than 32 bits, what goes in the "destination IP" field in the IPv4 packet that R is capable of sending? If S has an address that is guaranteed to be less than 32 bits then we're just in the IPv4 world.

How are R and S negotiating when R cannot even name S on the network? Its stack only allows for 32-bit addresses and S can't have a 32-bit address.
Came here to say the same thing. Unfortunately, they're not too easy to find, often expensive, and somewhat fragile. Mine didn't survive a recent move, and I haven't yet found an affordable replacement.
I think there may be a “Penny wise but pound foolish” thing going on in your analysis.
A couple of years ago I visited one of their meetings [Indieweb] in Germany. It was great fun. They are an incredibly friendly, open-minded and organised bunch.
> As for Git, it would benefit from using text format specifically aimed for easy diffing/merging. No idea how easy the sqlite dump is in this regard.

The problem I'd predict here is that then people would expect to be able to do three-way merges. It might even work correctly a lot of the time, depending on the exact pattern of changes. But my gut feel is that unless the schema were designed just right, there would be possible merges that would result in a database that was valid from SQLite's point of view but insane from the application's point of view (broke expected variants, etc).
In 10 years, at 3% inflation, cash loses about 26% of its value, and at 5% inflation, about 40% of its value.

Not "almost all", but that bucket is quite leaky.
The issues in Europe seem to be caused by Russia. What’s your point?
Funny enaugh, once an update rendered my Silverblue install unbootable. I had to boot to a live image to fix GRUB misconfiguration. Now I know it's not invincible, but it does work well otherwise.
The pro football Hall of Fame is in Canton, Ohio.

I guess it's near a regional airport. Still a pretty random spot though.
Duh, C also doesn't have fat pointers. And C doesn't have a runtime_sizeof keyword. How do you get from this to "The existing sizeof should be re-purposed to be evaluated at runtime"?
I know, we had something similar in the Netherlands (in fact we still do). An independent phone network for the government.

But my point is: You can protect the building. What about the trunk lines going all the way to those other bunkers? They're not immune to nuclear blasts and in the days it matters they were made of copper which can catch EMP directly.

These days they will be fibre which is EMP immune of course but the repeaters are not.
Yeah, I'd expand on the "API over DBs" based on my experience. I could make it nest much deeper: DBs over Excel spreadsheets, and Excel spreadsheets over PDFs or scraped HTMLs, yada, yada, yada.
But before I waste any time creating an API, my client wants to know if the project is even viable.
Haha, it's longer now than in that photo.
They are not updated, on purpose. This is the design now.
> Meaning, every implementation has to run on environment targetable and compatible wit sqlite

Well i get what you are saying, sqlite has been ported all over the place. It probably wouldn't be the limiting factor portability wise.
Well, the predecessor is stainless steel, which I imagine is closer to the Ti number, and in my experience with 12/13 Pro it's always the back that throws off heat, not the frame.

Anyhow, just the frame is this material, inside its Al.
Yes, it's extremely challenging for that reason. If you have another option please let me know. I just don't really have a network of people to ask and generally don't have time or know how to build one. So I would be happy for another site like Upwork without so much competition.

Although I think if you are willing to work for relatively low rates like me, being in the US makes you stand out and possibly easier to get hired.

Upwork does have an option to post jobs that only allow US contractors. And you can search for only those types of jobs if you are in the US. But often I take that off because it restricts the search quite a bit.

I think the reality is that since more and more people are working remotely, it's a global talent pool and kind of a race to the bottom in terms of rates.

I just wish that there was more competition in terms of sites like that.
There was a third option: make the existing IPv4 space a hierarchically routed island of the new IPv4.1 space, with backwards compatible packet format, then upgrade just the endpoints in the first phase.

So every owner of a ipv4 would get, say, an entire 32 bit space that routes over existing IPv4 infrastructure. So, if the endpoints are upgraded, you have guaranteed end-to-end deliverability without silly hacks such as NAT or STUN.

This doesn't solve the "backwards compatibility" problem itself, because you still have two logical different IP networks running on top of each other, requiring separate name resolution, etc. But what it does solve is the "incentive problem": endpoints are incentivized to upgrade because it gives them an immediate benefit, end-to-end connectivity to other upgraded users with non-routable addresses sitting behind a dumb, non-upgraded IPv4 routers.

For example, VoIP or P2P software would immediately benefit and it would drive adoption for an immediate use-case. In the later stage, when the entire infrastructure can understand the extended packet format, you would start to publish extended routes that don't fall into the hierarchical range, similar to IPv6 today.

IPv6 lacks any such incentive, because me upgrading and enabling it has zero benefits until all hops separating me from the internet also enable it and correctly configure it. On the contrary, by requiring a completely new, complex configuration with no "default, just works" mode, IPv6 introduces a disincentive, because by enabling it not only do I not gain anything, but I risk breaking my internet due to misconfigured upstream. So the conservative setting for IpV6 has, for the last 3 decades, remained "off". This only recently began to change.
As a startup it's not about scaling.

Either you have to scale than you should have the revenue or VC for doing so or you don't need it.

Cloud provider is about were to spend your resources: do you want to build features which make money or do you want to manage your deploy scripts and build monitoring etc yourself.
In practice IPv6 is for mass market ISPs and IPv4 is for servers. Wasn’t the intention, but that’s how it is to a first order approximation

There are billions of phones so sure, they should be on ipv6. ipv6 is a kind of super NAT that few people bother to learn

Sorry about that ipv6 committee
>> The file named by the INTO clause must not previously exist, or else it must be an empty file, or the VACUUM INTO command will fail with an error.

EDIT: there is no difference between VACUUM/VACUUM INTO - they both write to a new file (COW) it's just VACUUM [NOT INTO] does mv temp.sqlite originalfile.sqlite after that, while VACUUM INTO does not.
That is a good argument, however many people like some big game development company start to ship with GB of json file, at that point just use SQLite. It will be faster to query load. Also if you look at how DB such as Mongo (Not promoting them in any way), but when Maildir is used aginst Mongo for file storage, Mongo saves a lot of disk space. Again, it is about how we want to store files? NixOS is a quite a way to think about having a file system or db/store.
Europe in many parts seem to have failed to integrate many of the newer groups. Some have integrated well enough to be noticed. But Sweden well known for inclusivity have strange things happening in certain parts of country.
If you want the work done, why not just pay someone to do it instead of playing games with bounties?
> boils down to good old fashioned "system analysis". Know your system, every part

This type of answer has managed to talk me out of some amazing roles (and dodge some horrible people).

Apparently the correct answer is "there is a magic formula whereby you dont need to understand anything or do any analysis and it will deliver you sunshine and rainbows"
It does yes! But it's in the millions now, not tens of thousands.
> It's what their proponent claim that they are useful for, yet there's no single instance of a successful blockchain project actually achieving this kind of resource-sharing goal

Sia and Filecoin already work in this way to for people to share storage.

> In fact, it's likely that trying to add money into the mix will just break the system instead of improving it

This depends on the amount of money people are willing to pay for processing power. Volunteer contributions would be reduced, but the paid contributions could make up for it if the people who want to train their model pay enough to attract more people into the system and if those people can compete with conventional commercial offerings.
It isnt a bug it is a feature. There is a point in law sometimes being a bit vague to create flexibility
It's usually not a tehnical problem, but either a management or a budget problem.
Not to be confused with Office Open XML (OOXML), Microsoft's "standard".
Won't be going back to Adobe for the remainder of my career.

Photoshop CS6 + DaVinci Resolve

These run good on Linux too.
Thanks for providing the link, readers can probably judge for themselves by checking the comments there if blocking someone just for having a different point of view was the right thing to do by the Zig leadership team

Context: https://news.ycombinator.com/item?id=37545192
Can you quantify that though? I mean if you look at people who study writing in college the salary outcomes are pretty bad. Im not saying its not useful, or that its easy.
it sounds a lot like there is plenty of money to be made from the figures parent is stating. Maybe it ought to be prased more like "unique logistical challenges" because clearly some few companies have made it work very well
When you have to eject anyway, you would probably want to do it in an area where you can get help relatively quickly, due to it being quite a bit dangerous, and not in an area with no infrastructure or over the ocean.
Freegamedev.net
It's not like people didn't think of that when IPv6 was discussed. It was something like a decade from when the first IPng proposals came to when the proposals which looked like today's IPv6 came.

Bernstein was certainly part of that discussion, at the later stages, and the document you link to reflected that. It was just one of many counter proposals that influenced what became IPv6.

Some people seem to suggest that Internet standards are written in some ivory tower and dropped down on the network engineers to implement. In that light, such criticism of IPv6 would be valid and important. But the IETF does not work like that. You can take part, and I can take part, and any reasonable criticism is discussed in the open. In general, practical proposals and code is taken more seriously than loose ideas.

There is no central command which decides what you or any other network operator should implement. People all over the world implements what they think is good for their network, in order to interoperate with other networks. If anything, Internet standard can be criticized for being slow to fruition because of this open process. That's the price we pay.

It's not very useful to come 20 years later and re-hash the exact same discussion all over again. All counter proposals turned out to be impossible to deploy, and the consensus and running code we ended up with is what we call IPv6. A dual stack approach was the only solution practical enough to get general deployment. There are certainly problems with any protocol, and let's suggest improvements and new protocols. Just make them relevant today if they should have any chance of deployment.
We don't. Everything that is not part of the code will just get out of date.

It's just best to reduce external documentation, or at least bundle all in one place.

What works best is just creating a rough sketch of the idea, and store it somewhere next to the code with a datestamp. So it's clear that it's out of date, but if you really need some hint of how it was intended to work you can still look at it. (That is usually some class diagram, or a word document with explanations...)

Or it's just kept up to date by being used. E.g. we have step-by-step instructions for certain tasks, that devs occasionally need to follow. So if things get annoyingly out of date we just fix the instruction that has become unclear with time.
Yes to ALL of that.

I would add that a UI might prompt for a date as well, which of course would be entered using a local time input element based on the the users time zone. But that local time would immediately be converted to an int and passed to an API.
In sqlite the on-disk file format does not matter.

All that matters is that you should be able to issue sql to the sqlite embedded library and get back the results.

Freeing you from the overhead of owning (thus inventing and then maintaining) your own file format is almost the entire point of using sqlite in this manner.
> That tells us that people aren’t writing as much as they should, not that writing isn’t a valuable skill.

It depends on what it means by valuable. We may value it, sure, but in his example the poor communication didnt hurt their performance reviews or salaries.
It is not just fat32 and overhead up to cluster size; once I had 800k tiles in a single directory on ntfs.

It was unusable. The only thing that I was able to do is to tar it up and move to a machine with xfs, where I was able to sort it up into more balanced subdirs and then move it back (for processing using windows-only tool). Just tarring that single directory up took several days.
What to Expect at the Tokyo Games Show 2023
With annotated, declarative step-based YAML integration tests. They autogenerate how-to markdown documents via a jinja2 template:

https://github.com/hitchdev/hitchstory (there are a few toy examples listed there)

Depending on the app the docs might also embed artefacts generated under test - e.g. screenshots from playwright.
QCT QuantaGrid for Intel Xeon Max in Automotive CFD and CAE
Design docs are for the developpers. Technical docs could also be for the users, by e.g. ending up in some manual or so.
Have you seen modern anti-drone defence?

https://youtu.be/pb5_F4_Eod8?si=f8rmhs4ouaCKO0UE

Basically a cannon that fires sort of smart bullets that contain shape charge that aims at the drone as it gets close to it and detonantes. Also targets are smartly assigned so you can shoot down small swarm of drones with a short burst from the cannon.