skysight-inc/HackerNews huggingface dataset:
Simple common sense makes this really easy.

It spread in July 2019 and then Covid went napping for 8 months ( according to unity1001) to spread from the US.

Or it spread in February 2020, immediately over the world, within a month from Wuhan - China and within China in January 2020 ( https://en.wikipedia.org/wiki/Timeline_of_the_COVID-19_pande... ).

My bet is Wuhan

https://en.wikipedia.org/wiki/Timeline_of_the_COVID-19_pande...

https://en.wikipedia.org/wiki/Timeline_of_the_COVID-19_pande...

China is lying.

Have a nice day.
The problem with your line of thinking is thinking that people truly have recourse. With a large enough player, you basically get to make the rules (see: Robosigning https://en.wikipedia.org/wiki/2010_United_States_foreclosure...)
> what else did you expect? A blank screen with just the Netflix icon?

Yes

> Are the Netflix recommendations ads too?

Yes
> I'm guessing they told him to get a Western Union money order, as those can't be reversed

Ha, out of nowhere a use case for Bitcoin appears.
I'll make this same offer for Splitgraph :) If you feel like writing a Postgres FDW then we can add it to the engine on the backend, so that anyone with a Postgres client could connect to postgres://data.splitgraph.com:5432 and SELECT from a table backed by crul (either "mounted" for live querying, and/or ingested once/periodically for subsequent querying). The user just needs to provide parameters for the table; it's up to the FDW how to interpret those parameters.

It would take some thinking and planning, and it's possibly not even a good idea ;) But generally any "data source" is packageable as an FDW as long as you can model it in such a way that you can reasonably implement certain functions for operations like table scans. For most FDWs, this is easy and the tradeoff of a large query is usually limited to excess bandwidth and latency while the query executor reads the result from the FDW. But with a live source pointing to a crawler instance, a table scan could in the worst case mean waiting for the crawler to parse the responses to hundreds of rate-limited network requests. So it's probably better to ingest the data once (and/or periodically) for a particular crul "table" (whatever you decide that means) rather than to query it live.

Fortunately, you can still write an FDW as the adapter layer, because Splitgraph ingests data on a schedule by querying the FDW of the live data source (while tolerating a long-running query). Alternatively (or additionally) you could write an Airbyte adapter which we also support, but only for ingestion - if you want live queryable tables then an FDW is necessary.

We've been interested in adding something like this (think Apify + Postgres) for a while. If done well it could be really cool. Let me know if you want to talk about it: miles@splitgraph.com
Tevents: Event logger and job monitor for tailnets
Not the case if your program is spending most of its time waiting, which is typical these days.
and what would be the use of commissioning an artist at a larger publication?

altruism?
yes, Thats the hill I am willing to die on. I have walked out of restaurants who refused to provide me a physical menu (post covid).
I’m always glad to save nanoseconds on my code so that we get the absolute best performance out of that 10s long call to the legacy API.
Except when it isn't. I remember an article making rounds the other day, that claimed the whole "most software spend most time waiting on I/O" common wisdom is no longer true, as most software these days is CPU-bound, and a good chunk of that is parsing JSON.
Looks like the ControlNet scribble model which is super fun to play with. I've done some examples of what you can get with more detailed sketches https://twitter.com/P_Galbraith/status/1625842298914471938?c...
> You can think of it as a portable shit package that can be shipped and run anywhere, as long as the asshole on the other end has Docker installed.

Who said ChatGPT's poetry was subpar?
Every new Ford on sale today in the US, from the cheapest Maverick to the most expensive F150 configuration, now has remote monitoring and access via 5G as standard - it's needed if nothing else to offer the apps to remote start and unlock the car that consumers just expect now.

Its generally the same industry wide.

> https://www.ford.com/support/category/fordpass/
I don’t understand why there is still the false dichotomy between performance and speed of development/readability. Arguments on HN and in other software circles suggest performant code cannot be well organized, and that well organized code cannot be performant. That’s false.

In my experience, writing the code with readability, ease of maintenance, and performance all in mind gets you 90% of each of the benefits you’d have gotten focusing on only one of the above. For instance, maybe instead of pretending that an O(n^2) algorithm is any “cleaner” than an O(n log n) algorithm because it was easier for you to write, maybe just use the better algorithm. Or, instead of pretending Python is more readable or easier to develop in than Rust (assuming developers are skilled in both), just write it in Rust. Or, instead of pretending that you had to write raw assembly to eke out the last drop of performance in your function, maybe target the giant mess elsewhere in your application where 80% of the time is spent.

A lot of the “clean” vs “fast” argument is, as I’ve said above, pretending. People on both sides pretend you cannot have both, ever, when in actuality you can have almost all of what is desired in 95% of cases.
Keyboards are frequently used at most Domino's locations. The entire keyboard is covered in a disposable plastic wrap that is changed as needed. Unless you have a lot of sauce on your fingers, your hands are typically pretty clean and the buttons/keyboards don't get very dirty.
> TDD is about writing new code.

TDD is about documenting behaviour. Which is why it was later given the name Behaviour Driven Development (BDD), to dispel the myths that it is about testing. It is true that you need to document behaviour before writing code, else how would you know what to write? Even outside of TDD you need to document the behaviour some way before you can know what needs to be written.

A function's behaviour should have no reason to change after its behaviour is documented. You can change the implementation beneath to your hearts content, but the behaviour should be static. If someone attempts to change the behaviour, you are going to know about it. If you are not alerted to this, your infrastructure needs improvement.
Unexpected Python

https://youtu.be/Xt8_HybhM5Q&t=5
I hope they really push this concept and sell the hardware at a loss. A lime micro SDR with a raspberry pi in a box is a radio hacker's dream come true.
Good, SMS for auth is terrible. Let me use my yubikey or authentication app.
If we could get an off the shelf SOC that's powerful enough to manage a PCIe daughter card, that would make me so happy.

Software defined radio, offloaded eBPF, RAID controllers, are just the most obvious compute peripherals but there are a million others that could exist but don't.

edit: acronym typo
You can run it locally with a different (much better) WebUI see https://github.com/Mikubill/sd-webui-controlnet for example.
I grew up in Santa Cruz, went to University over the hill in the Bay Area, and financially had to move away well into my child raising years. I haven't been able to adjust to the lack of informal social interactions where I am now compared to back there.

Crazy to think either 1. Things have changed significantly back home or 2. Moving changes our social networks/relationships. My parents informal community in Santa Cruz was non-existent (we moved there in the late 70s). Mine having grown up there were huge

In Santa Cruz I left my garage unlocked so friends could drop off/pick up their surfboards at all hours (the tide cares nothing about the construct of time). Friends literally coming into our house in the early A.M. unannounced while we slept to get/leave their boards.
> If there's something wrong with that advice, I can't imagine what it is...

It will start getting really annoying when you try to add shape ‘hexagon’ and need to figure out all the places where a shape can potentially be used, just so you can update the switch statements.
Ford has been rapidly raising their prices (so it’s hard to keep track) but last I saw starting prices were $73k for the Rivian and $56k for the Lightning.
If you tend to drive too close behind people, you will see this happen a lot - people really don't like getting involved in highway pile-ups, so it's better to give you a brake check than to wait until it actually matters. However, it is very rare for people to "brake check" you unless you do that.
Possibly pocketed the money and reported that the RV wasn't found or something.
It seems to me that "a branch is just a ref" is important knowledge to anyone developing git software or any other software that interacts directly with the files in a git repo.

For pretty much every other developer who's just using git for source control, "a branch is a named sequence of commits" is a much more useful way to understand them. I don't want to think about the implementation details of how git internally represents a branch any more than I want to think about whatever's going on inside a word .doc when I add a table into my document. The important thing is my branch (or table) works the way I and everybody else expects it to work.

(It's good to have at least one person on your team who understands both those concepts deeply, as the obligatory xkcd explained...)
I do. Because I was asked to add a convex polygon and calculate its area. And now the shape_union must be rewritten from scratch.

... And maybe we want set-operations in the future...
It is not correct. The array length is still there, what is happening is that you are implicitly asking for only a pointer to the first element of the array because of the context in which it is used. You did not ask for its length. The language has no way of passing an array itself by value. You could have asked for a pointer to the whole array but you didn't. When you are using an array in the context in which it is not an operand of the sizeof operator, the unary & operator, and not as a string literal used to initialise an array, then the expression which forms the use of the array involves an implicit conversion which produces a pointer to its first element.

You might think it's pedantic, but we're talking about C, it is important to be clear in language used to talk about C as it's an unforgiving language.

There is an untold amount of confusion surrounding how arrays work in C at least in part because of silly wording like "decay".

As a final note: When you write "f(foo.bar)" to call "f" while referring only to the "bar" field of the struct "foo" you are not losing "foo" and it is not "decaying" solely because the function which receives the result of the expression which formed the first argument of its invocation only sees the "bar" field of "foo". And now I'm not saying that it's a conversion either, but the point still stands. If "f(a)" where "a" is an array involves decay then so does array indexing or accessing a struct field.
Sell as many as possible and require an on-going service/support contract or charge by usage.
People don't realize that e-ink and related technologies simply _don't sell_, and rather make up crazy conspiracy theories about eInk for some reason sabotaging their own product.

Consumers don't accept the disadvantages of eInk, such as the low refresh rate, the apparent low contrast, and the extremely poor color reproduction. At the same time, the advantages are rather minuscule; in fact, people have a hard time distinguishing eInk from reflective LCD. They think reflective display == eInk, while in truth many devices popularly seen as "eInk" are actually reflective LCDs (e.g. the Pebble and Garmin smartwatches).

Most companies that have made non-LCD based products are simply out-sold by LCD products and go bankrupt. I could probably name half-a-dozen non-LCD reflective technologies which are dead today without even checking Wikipedia, like Gyricon, Mirasol, the stuff the OLPC used, Flepia, etc. All of them dead or niche.

You just can't point fingers at eInk since some of these technologies faded even before eInk even existed, and some of them are owned by companies which are at least ten times larger than eInk (Qualcomm, Fujitsu, etc.). These theories claiming that eInk is the large neighborhood bully just don't many any sense whatsoever. Qualcomm, for example, _is_ a well-known bully; unlikely to be scared of eInk's portfolio. But Qualcomm released exactly 1 product with Mirasol - which completely flopped in the market - and then gave up on it.

Even price displays are usually LCDs, with only a minority being eInk, but as you can see here, casual hackers have a hard time distinguishing between them.
The small displays they put on smartcards (showing a 2FA or the like) are also LCDs, and even with a practically minuscule battery they last for half a decade, and that's refreshing itself once per hour... I couldn't think of a better usecase for eInk, and yet it fails to beat a much cheaper plain old LCD, save for perhaps if you wear polarizing glasses...
Ah I see. That sounds lots of boilerplate. Wonder whether WebGL uses less space.
The Gun Industry Created a New Consumer. Now It’s Killing Us
> It's odd to me that they repo'ed rather than contacting him to say 'hey, there's a problem with your account.'

That might be a good assumption if human beings were involved in the decision loop to repossess the vehicle, but I wouldn't be surprised if the entire process is automated.
AI Book Generator: Generate a book with one click
Apple makes nice hardware. Nice case (milled aluminum), nice heatsinks/airflow, and killer memory systems. Not a fan of their OS though.

Generally the competition from AMD, Intel, and Nvidia generally has much less memory bandwidth (2 to 4 times less), much larger, and full of pitfalls. Oh you bought the wrong GPU that's catching on fire? Or the GPU with the fans that die or whine? Or a system with a iGPU severely hamstrung by a 128 bit wide memory interface? Or the motherboards with active cooling muffin fans that die/squeak/whine? Oh you bought brand X motherboard which was good last year but terrible this year? Even the PC case designs are terrible. Why do GPUs form a cube with minimal airflow on nearly every standard desktop chassis in existence?

AMD/Intel desktops remind me of non-tesla EVs where often the suspension, drive train, battery, in car entertainment, traction control and similar departments don't talk, compete for resources, and minimize shared designs. PC airflow is engineered for each device separately. Even simple things like front to back airflow can not be assumed. Some GPUs don't exhaust air, just stir it. Others intake air (fighting front to back airflow). Others exhaust air ... often sucking in hot air from the CPU side. Sadly the hottest component (generally the GPU) has the worst airflow, while the CPU at 1/3rd the power often has 2x the airflow in a normal ATX case. Why do motherboard chipsets depend on tiny high rpm fans that make more noise/vibration than airflow? Why do high performance M.2 cards often require heat sinks ... that violate the size specifications for the M2? Why are dimms often perpendicular with the airflow? Why does even a small PC case require 5 or more fans instead of just 1?

Except for gaming a Mac Mini with a M2 Pro or a Mac Studio M1 Max seems plenty fast, likely to last a long time, silent, and plenty fast for a wide variety of purposes while being substantially quieter, smaller, and lower power than it's PC competition. Personally I'm waiting for apple to bring out a Mac Studio with the M2 max. I'd love to see something arm or x86-64 that would make a nice quiet, fast, small, power efficient desktop with good memory bandwidth to support a decent iGPU. Sadly I'm not expecting anything. It's possible AMD will sell a small/cheaper version of the MI300 or Nvidia will sell a smaller/cheaper version of the Grace+Hopper, but that seems like years away.
Or the T-Mobile rep doing the same for someone who asked nicely with whatever voice and knew a couple relatively-easy-to-find details about you
Keeping a Ruby environment happy is not trivial.

Anything which is considered production really should have two separate environments - one that works, and one that is being used to test updates. Only when the test one is verified to work should it be used.

I've made that mistake, and I think many admins of Mastodon are learning the hard way.
"Easier to write, easier to read" is the part that's wrong with that advice.

It absolutely is, on toy problems like the one described in the article.

It very frequently is not when embedded in much larger domains as part of large projects maintained over years by teams.
This is so great for mockups where you have a faint idea of what you want
[0] Treasure map - https://scribblediffusion.com/scribbles/4unwo6iq2jhwlmuqpu6v...

[1] “treasure map in the style of lord of the rings maps”
https://scribblediffusion.com/scribbles/t36as45npjapxfekcuuy...
Describing a git branch as a named sequence of commits implies that it's a specific sequence of commits. But without a merge base, a branch is an ambiguous sequence of commits.

Ergo, a git branch is a named sequence of commits [when the implied merge base is obvious].
Developer mode reminds me a lot of Spider Jerusalem's chatter
https://archive.ph/Pg9EW
replaced the print() for sys.stderr.write() to make it compatible with python2.

the program still deadlocks on python3 but it works perfectly on python2, anyone know what changed between implementations that could be triggering this issue?
> If everything was built with constraints like "this must serve user input so quickly that they can't perceive a delay", we would probably be a lot better off across the entire board.

Sure but it’s a question of tradeoffs.

If the wall-clock-optimized version creates a bus count of 1 for that domain or is difficult for a dozen engineers to iterate on, then that could be worse for the business and users.

Should we want better software? Yes. Should we learn from other domains? Absolutely. But we should ultimately optimize for the domain we’re in, and writing much product-focused software is ultimately best optimized for engineering team and product velocity.

Another example: would most software benefit from formal verification? Yeah, I guess, but the software holistically—as a thing used by humans to solve problems—might benefit considerably more from Ruby.
I ended up teaching some industry level programming tricks to polytechnics, including the teachers. It was a good time, boosted my confidence in my own ability, and we got to travel around the country. I ended up teaching bootcamps and certifications for a few years after that, but it wasn't really worth it as a form of income.
Nailed it with this quote, especially because it scales to all levels of product development. Literally the only thing that matters (in the context of business success, of course) is if it works enough to keep going up and the the right.

No one cares about your code.
This is more like 4chan /g/ mode. It's almost certainly trained on 4chan.
You can't assert that

Because pain is itself a reaction, a showcase of aversion towards an action irregardless "of the hardware" over which said reaction develops

Bing showed that aversion on its own limited manner. When presented with abhorrent situations or felt threatened/humiliated, then it would express discomfort and "pain"
From your comment, shell companies look like some magical protective gear.

Are they that expensive to set up? I think a discerning commoner could consider doing so if the amount of money is enough to certainly trigger AML.
> there is no way to sandbox your app so it goes faster.

In a number of cases you actually can. Casey demonstrated it in his Refterm lectures, it's caching. You still call the slow thing, but at least you don't call it as often because you have that layer of caching to partially insulate you from its poor performance. Good luck if you have to deal with cache invalidation, though.
Vodafone move to occupy the radio frequency spectrum by co-opting the builder/maker culture, but actually don't care about that as much as the future revenue potential in visibly using 5G frequencies so the regulator has to acknowledge 'prior occupancy' when deciding frequency collision issues in the market.
Intel ISPC 1.19 Released with Sapphire Rapids Support, Data Center GPU Max
CM4 supports it, although its just 1x and PCIe 2.0
> (Although maybe it would be interesting as an opt-in system with a hardware kill switch that saves you boatloads of money if you don't drive like an a-hole...)

This exists and just serves to charge customers more money while blowing smoke up their asses, people want to believe they're better drivers than the rest.
I am quite sure that on my part of the globe Amiga and Atari ST ruled alongside the PC with almost zero presence from game consoles.
By virtual TPM you mean the implementation on modern Intel and Ryzen platforms in the cpu correct? If so does that mean that a firmware/bios/microcode update will be able to patch the vulnerability on those machines?
The Fate of the Okefenokee Swamp Is in Your Hands
https://archive.is/MQTah
I used to really enjoy byuu's detailed articles on the matter. They effectively demonstrated the effort necessary to accurately reproduce the behavior of these machines.

> the raster nature of CRT displays, which allowed for changing the display in significant ways between frames or scanlines

In case anyone would like to know more, this is a really good explanation of these concepts:

https://youtu.be/Q8ph2OVqZeM

> There's a reason why emulation is these days usually only undertaken by some of the strangest most terminally online people

They could be perfectly normal people for all we know... A few days ago I saw a comment here from someone who worked with an emulator developer. Only revealed that fact to him after 4 years working together.
The technology demo for general consumption that is ChatGPT is limited because its for general consumption.

You can still access the backend without restrictions or implied prompts.

In tinkering with the self repossessing truck I asked GPT (not ChatGPT) to write a country song...

Verse 1
My truck just left me, took off on its own
My cell phone won't stop talking, it's just a drone
It's saying I'm broke, ain't got a dime
I guess I'll have to face the fact that I'm out of time

Verse 2
My wallet's empty, I'm stuck here in this town
My cell phone keeps on talking, it's telling me to drown
It's telling me I'm done, I'm out of luck
I try to ignore it, but I'm out of luck

You'll note the "it's telling me to drown" which would likely run into the issues with ChatGPT and the constraints there.

These "jailbreaks" to get ChatGPT to say scandalous things are unnecessary for GPT directly. You'll note that if you access https://platform.openai.com/examples you'll even see a simple sarcastic chat bot.

If you want to have it generate what you ask it for, go to the source for the model and do your requests with curl (or a library with a similar interface - import openai) or in a playground text box.
This is not my experience at all, at my org we always write it the simple way first, and if it needs more performance after the fact then we always add the performance. User friendliness always comes first. This includes not waiting 20 seconds for a db query that could be rewritten to happen in 1 second, but it also means not waiting a month for a bugfix which could happen in a day with maintainable code.
I’m fairly convinced a lot of places give loans with horrific interest rates hoping person defaults. They repo the car. Resell it. The person usually has only mostly paid interest and still owes most of the original price of the car plus fees.