skysight-inc/HackerNews huggingface dataset:
A much bigger issue that I keep seeing not getting enough emphasis is when the real rates go up US will have to keep raising their debt ceiling substantially to fund their debt (34 trillions and counting). If the last deb ceiling raising debacle was of any indication, this will be a very difficult political process in a rising rate environment, not to say US having to pay for interest expenses equivalent to another military when rates go higher by a mere 2-3% is not far fetched anymore at this level of borrowing. So something is got to give, either there is sovereign default which is unlikely or stagflation of some sort with rising rates, I don’t know. I just don’t think Fed is as independent as people would like to think they are.

Also May be I am a moron but how does raising rates help the supply chain crisis when all else said that is what’s behind driving the inflation (at least that’s still the narrative from the administration and mainstream economists)? I mean if the expectations is Americans with their 2 trillion households savings are just gonna start shoring up their cash and stop spending because the rates went up by 75 basis point, I just don’t buy it. May be the Feds don’t want inflation expectations become embedded which I understand even though that seems to be the reality at least for a while till at least 2023.
Personally, I travel a lot. I can barely keep plants alive when I'm gone, so an homestead is not feasible.

I don't want to commit to the constant effort homesteading demands. I can currently drop everything and leave at a moment's notice. I can work remotely for as long as needed. A homestead would tie me to a place.

I also like living close to the city and its variety. I don't like the areas where homesteading is possible.
FYI, the 68060 was fast, providing a good upgrade path from the 68040s found in a4000s.

Near the end, after the initial bankruptcy, PowerPC boards, some with 060s and PPC chips both, hit the scene.

Entire SDKs were introduced, and many bits of software were ported. This was a good bridge, and as Apple made this sort of jump, eg, they didn't die when switching from 68k to ppc, I don't think a healthy Commodore would have either.

So I disagree. The Amiga could have transitioned too.
I still remember dialling into my university account back in the very early 90's and running X windows over the connection at a friends house.
The money printing press that is chip maker TSMC
Why don't they borrow $250k from somewhere else and pay you?

Spoiler: because it's easier and cheaper for them to sucker you into doing work for IOUs.

Ask for the cash or a piece of the company. Once you hand over the code, you don't have a lot of leverage.
I had that exact experience in 2021 at DEF CON, I was attending the physical part of their hybrid format and it was quite awesome and felt relatively safe.
Wouldn't infinite temperature object emit infinite amount of energy at all wavelengths, making the spectrum (and color) ill-defined?
What linters are you using?
Ask HN: Google Guice another abandonware from Google?
It's been already 4 months since JDK17 was released, but Guice (one of the most popular Java dependency injection frameworks) still didn't release required compatibility changes [1]. There looks to be zero contact with maintainers at Google. In the meantime Spring was ready for JDK17 in July (3 months before JDK17 GA) [2]

For years I advocated to use Guice at my companies, as it's considerably less bloated than Spring. Now I'm starting to get some heat on this as it's clear that the support is just not there. Is this the right time to accept the defeat and start migrating back to Spring?

[1]
https://github.com/google/guice/issues/1536
[2] https://twitter.com/snicoll/status/1420652097373188100
The problem with sql is what happens when you fall off the SELECT FROM JOIN WHERE GROUP BY HAVING ORDER BY LIMIT cliff. The simple stuff in sql reads like English, but for that case ORM would generate a pretty efficient query anyway. The complex stuff in sql looks terrible in my experience and ORM bail out quickly. Once you can’t get the result with a simple SELECT then sql stops being declarative. Instead of writing what you want to get, you write something like a postmodern poem while having a stroke, just to convince postgres benevolent spirits to give you something almost right. Complex UPDATEs and DELETEs with joins are even worse.

Also lack of syntax sugar doesn’t help. SELECT list could support something like “t1.* EXCEPT col1, col2”. Maybe JOIN ON foreign key would be nice. IS DISTINCT FROM for sane null comparisons looks terrible. Aliases for reusing complicated statements are really limited. Upsert syntax is painful. Window functions are so powerful that I can’t really complain about them though.

We use a lot of sql for business logic, but some code I have to reread from zero every time I need it. Maybe we modeled our data wrong or there is some inherent complexity you can’t avoid, but I mostly blame sql the language. Unfortunately I have no idea how it could be improved.

Anyway I think the sql cliff is real. Once you take a step outside the happy path prepare for a headache. For me sql definitely is in some local maxima, after all I use it every day at work.
I agree, better a mediocre standard than none.
Out of interest, for Javascript there are many languages that transpile to javascript but support quite different approaches like functional programming, strongly typed, etc.

Is there something similar for SQL, where you allow an alternative syntax and maybe programming approach and then use SQL as connection to the DB ?
> Is there any reason why official python doesn't have any JIT option?

Desires to keep the implementation simple and approachable (relatively), as well as avoid issues of performance cliffs and such.

Also the C API has historically been extremely broad and provided large access to what amount to implementation details, making this keep working properly with a jit is difficult (at least for anything but a simplistic macro-ish JIT).
Related, from 3 days ago:

https://news.ycombinator.com/item?id=29935939
The problems I see here are:

1. The parameter was named accessSecret, but the environment variable was (...)ACESS_TOKEN_SECRET. This type of inconsistency can easily confuse a human programmer as well.

2. The programming language (JS) allowed an extraneous parameter to be included. Languages with stronger typing would at least allow the IDE to mark the parameter as unused/invalid.

3. The library didn't complain about a missing important parameter.
> I just use linters now and presto literally all of my problems ever with YAML gone.

Copy a valid fragment of YAML from one file into another file, run the linter, and presto! garbage. Whitespace-indented formats are poison for auto-formatters. They might have made sense back in the 90s when such "advanced" tooling was rare, but they're a bad choice today.
Intel Raptor Lake Could Pack a Cache Upgrade for Gaming – HotHardware
They owe you 250K, or their employees?
The EU has tried to put one in place, and it is used for all EU funding programmes and by a number of national and local administrations in Europe, so probably tens of millions used per year.

Not sure I like the format but its good it stresses experience and narrative over just 'formal' data. And they have done it quite nicely that you can either download a template and work offline, or you can work in the browser and then download later again upload/import your CV to continue editing, make versions, etc without any data being stored on the server.

https://europa.eu/europass/en
DirecTV Dumps OAN, Leaving It with No Major TV Distributor
I just used apktool to debug an instrumentation issue, and it was a great help. I'm glad I learned that skill.
Yes, I'm sure of it. If anything, it is the opposite of what you would learn in Disney. There are people in the concentration camps who did not steal or who even gave away the food they had to help others, people who go on hunger strike until they die for principles, there are people who go to certain death in war on principle, lots of examples of people who would die to protect their family rather than abandon them, and there are examples of people helping others get the safety/on the helicopter harness until they themselves die (and that's where saving themselves wouldn't even be viewed negatively or break a personal belief, it's just pure unselfish helping others at the cost of your own life). Those principles, or the resilience of them, may be uncommon or even rare, but it is definitely possible to have a stronger desire to have integrity and comply with a belief system than to live.
The argument feels like a straw man.

He seems to be saying, if your password selection strategy skews towards really weak passwords, and you measure the Shannon entropy of the distribution, it won't reveal that this is a bad strategy.

I don't know anyone who would actually do this and declare a win "because Shannon".

At best, it's mildy interesting that Shannon entropy on its own isn't going to give you a useful answer if you have a weak strategy.
> This file was also checked into a global CVS archive that all project members had access to. Today one might use GIT or SVN but any revision control system would do.

Having locally created sequential ID's seems...strange. Or you simply have so few people creating ID's (and committing them so quickly) that it's not an issue.

There are tons of ways of resolving this (such as author-prefixed ids "joe-23"). But simply calling it ticket++ in a global shared directory seems it could become a source of frustration and honestly a pretty inelegant solution to the problem. He mentions "doing one thing and doing it well" and being a "minimum viable program". One could argue that doing ONE thing reasonably when it comes to creating database records, is allowing me to create one without a conflicting ID. If the new_ticket command is actually immediately creating the entry in the central repository, retrying until it successfully allocates the next ID, then it works I suppose.
> House of Windsor ascended to the throne of the United Kingdom in the misty past of … 1901

Just because the 1901 successor to the monarchy (Ed 7) was the son of a reigning queen (Vicky) rather than the son of a king does not make him unrelated to the previous dynasty. Agnatic primogeniture is just as much a bronze age concept as a particular family lording it over everyone by the gods' grace...
Because life is Turing complete.
It was fine until apps ended up doing everything on their end and push pixmaps to the X server. Back in the xaw and motif days, it was fine.
Bad journalism in the past, does not mean journalism isn't worse today than it was overall 50 years ago.

This erroneous argument I see frequently is similar to saying "botched surgeries happened in the past, therefor modern surgery is just as bad as it's always been."

...and then I can go on to list three anecdotes like you did about individuals who died under the surgeons knife 50 years ago.

It's not logical. It's also hard to imagine it as being an honest argument. Can you honestly tell us that you haven't noticed a decline in the quality and accuracy of journalism over your lifetime? The contrast from my perspective is blatant and staggering.
This just don't work for interoperable protocols (or file formats). If you have a protocol with multiple implementations, they may be written in different languages, with different XML libraries.
Try writing unit tests with Copilot and you won't want to go back. When it comes to simple repetitive code like that, it excels.
EC2 is their oldest service; I bet it has oodles of legacy workflows both on Amazon's side and on customers' side. Lambda is likely a much lower hanging fruit in terms of the effort required to make changes to it.
That's not always possible & wise, e.g. the example given is the Kubernetes search/ndots values. Changing this would break the expected "API" between the applications in Kube and the Kube cluster, which is bound to cause some pain and suffering down the line :)

Using a FQDN (as in, a DNS name with the trailing dot) is the only reliable way to avoid this without breaking other things!
Reverse engineering of Japanese music video games has been a huge issue. I was grown up from the environment where the only way to enjoy those games was an illegal means for a long time, and even at that time the contention was evident. In fact the article missed important details like that Konami moved to online authentication as a direct response to a massive content leak in 2012 among others, and that Programmed World (or later, Programmed Sun) was commonly used by gamers from Japan and other Asian countries where those games are legally available---even after the invitation-only policy and geofencing to prevent them. Made essential due to the COVID-19, the end game for those arcade game publishers seems to be the de-arcade-ization; Konami has been particularly active at mobile and PC ports of their arcade games and that greatly reduced the needs for legally questionable practices.
Hey! Thank you for 8bitnews. I don't remember a single "newsletter" I was actually happy to receive before it. Great work!
That is great for all the people who prepared their CV in this format and avoided an employer who is unable to appreciate standards that work across borders or to realize that the information is more important than the format...
They should. You are correct on that.

Reality is, however and in my experience, that more and more HR departments fall for promises of AI snake oil. Virtually every employer I apply with has it's own portal, often times asking you to construct your CV anew on their website (often with drop downs that don't include the actual job title or skill). Preferably with a five minute web session and no submit confirmation. Couple this with companies increasingly not responding at all due to fear of being sued, and you'll spend hours on an application and won't even know whether the non-response is due to you, or due to the website trashing the submission. As for CV parsing, this has gone so far as to a big news site over here posting helpful articles on how to beat the system. "Favorite" tidbit: Submit two CV - one for humans, one for dumb algorithms.

Oh and btw, I'm applying at non-tech companies increasingly. Maybe humans isn't perfect either. I mean, I submit proof of 25 years of high grade enterprise IT experience, just for some HR person to ask me where my certificate as an "IT technian" is: they don't know what any of that "weird stuff" means, but to them I lack a generic "IT technician" certificate in early career. A thing that didn't even exist back then! But the latter may just well be a quirk of my own, bureaucratic country.

But overall, this is a hot mess already, and I have often times had the same thought: Why can't we have some sort interchangeable format, much like "geek code", just for all the possible job titles, universities, locations, and companies; with some format-dependent, but free text fields because one can never catch all of them in a fixed list?
Though playing around with this offline is not exactly difficult either: you can just invoke `dis.dis(codestring)` at the command-line, or use `dis.dis` as a decorator when defining a function (it automatically prints out the bytecode).

Sadly `-mdis` requires feeding a file by path or data through stdin, so for mucking around it’s not the best.
https://www.timeanddate.com/date/february-30.html
"Developers" (I use the term loosely) coming from e.g. React are getting used to storing data in a global state. The Redux library lets one change the value in the global state, and all places that use the value are updated "automatically" (e.g. by tons of behind-the-scenes code that the "developer" on his brand new mac doesn't notice, but users on five year old Windows machines with a dozen open tabs do notice). Vue has a similar implementation, Vuex.

When not using React or Vue, people used to these conventions will not know how to properly pass state between objects. This library is for them. It really offers little more than `window.pets.dog.species = "poodle"` would offer but because it is a library it feels "less hacky".
I mean, ideally you have a breaking break-in so that you have evidence for the insurance that you have, in fact, been broken into. Best to have a lock that is easier to break than to pick IMO. But yeah, the base premise is that it should avoid crimes of opportunity. Like the steel cables to lock laptops and screens to tables; they won't stand up for a pair of sturdy snips, but they can't be snatched up quickly.
Which is a weird behavior by the library. It should complain when it is supplied no secret, and not just blindly send the request and hope for the best.
I agree that the bickering is tedious and old at this point (and perhaps has been since the start), but there is a sense that the technical arguments miss the point of what the contention is about. Now, my argument is based mostly on conjecture and observation, and I mainly use XMPP because Conversations is the only thing that runs on my Blackberry Q10 (another thread entirely); I have not much of a horse in the race in any other way.

Though XMPP and Matrix are diametrically opposed in terms of their protocol semantics, and can be meant to occupy different use-cases at their edges (say, message passing vs. eventually-consistent data stores), their core use-cases are much the same: one-to-one and many-to-many messaging for both public and private groups, in competition with other, proprietary applications occupying the same space (e.g. Slack, Signal, Telegram, Discord). For sure, it might be agreed that there's a wide spectrum of difference even in the aforementioned proprietary applications (the whole banquets and barbecues notion), but I'm hoping it's not controversial to think that one can implement an application in the same UX vein as the proprietary alternatives using either XMPP and Matrix.

That, I feel, the the core of the contention -- that somehow Matrix has wrested focus/effort/velocity away from a still-viable project in terms of end-user-goals, thus somehow dooming it (or open-source/community-owned messaging in general) in the process. At face value, this might very well be nonsense; if XMPP cannot compete, or is not viable, nothing anyone outside the project does will affect this fact. Conversely, if Matrix didn't exist in its current form, it might not exist at all -- it's not a foregone conclusion that efforts would've been poured into XMPP or whatever else instead. In any case, competition is generally thought to be a good thing, insofar as it helps drive competitors to improve.

Emotionally, though, I think I understand the contention, and I've seen it happen not with protocols, but with things like Linux distributions, where people would lament the proliferation of disjoint efforts, where no clear, viable contender to the proprietary solutions existed at the time -- and some might argue does not exist still; nevertheless there's not much lamenting nowadays, where multiple viable distributions and desktop environments exist.

In some sense, community-owned messaging is still in a precarious state, and splitting up efforts, as it were -- since efforts are not just split in protocol implementation, but also in the ecosystem of applications etc. -- makes it feel even more precarious. Whether there's any rational basis to this, and whether either protocol has a technical advantage over the other, I don't know.
5:25, not terrible. Couple of them I was able to brute-force, some of them I realised the easy solution as I was brute-forcing! It's fun, :not(...) is godsend.
Human nature. Some people will use code review as a stick to beat you with or an opportunity to show how clever they are.
The MMS content is hosted on a public HTTP server which the ISP themselves host (I'm not entirely sure anymore how the synchronization works). Yes, you may call it a proxy server, but since the data is temporarily cached I call it a proxy server, also the APN settings call it MMS proxy. The definition is pedantic.
ModernCV? https://ctan.org/pkg/moderncv
This change doesn't really do anything to remove the need for an API gateway or ELB.

However, with some Javascript it has always been possible to call a lambda directly from a web browser, it's just a bit complicated, and you can't use it to act like a general http webserver, the way you can with a lambda "proxy" integration.

https://www.mbejda.com/invoking-aws-lambdas-on-the-browser-c...
> This article ignores the most common problem I have with DNS these days which can roughly be construed as: What is actually handling resolution on my system?

This does my nut in too - even just narrowing the Q down to modern Linux Desktops with e.g. chrome/firefox, and I have absolutely no idea what the query path is. So many components have been added to the path over the last few years :(
sorry I hate to be that guy but its not non-challan, its nonchalant. I was confused for a minute their by what non-challan meant ... i was thinking tthat maybe it is related to https://en.wiktionary.org/wiki/challan
I guess that instead of transactions there is undo/redo stack, a.k.a. checkpoints [1]

[1] https://tinybase.org/guides/relationships-and-checkpoints/us...
my kids (5, 7) got a Lego Boost for Christmas this year.

they've spent basically 4 whole days with it with breaks for food and sleep. it was amazing. Lego has found a spectacular balance between physical play and screen time.
How is the Dropbox UI such garbage?
Once upon a time there was the matchbox server at Stanford University Wearable Computing Laboratory:

https://news.stanford.edu/news/1999/february10/webserver210....

https://web.archive.org/web/19991128033948/http://wearables....

>The Matchbox Webserver, which is serving this and the other web pages to you, is a single-board AMD 486-SX computer with a 66 MHz CPU, 16 MB RAM, and 16 MB flash ROM, big enough to hold a useful amount of RedHat 5.2 Linux including the HTTP daemon that runs the web server.
But isn't the whole point of Docker having a 100.0000000% repeatable environment? And how would that portable Dockerfile would look?
Isn't it BSD [1]? Anyway it became BSD only in 2000. It was $69 before that year. Of course everybody started using Linux because it cost zero. Linux didn't end into Intel's CPUs probably because its GPL.

[1] https://en.m.wikipedia.org/wiki/Minix
My current (air gapped) development environment includes CDE 1.6.2 on Solaris 10. At some point some devs found this to be a bit... dated, and decided to roll WM flavour of the day: Fluxbox. Sadly, one of the X components was missing from Solaris. No problem! One dev hacked together his own version in Perl based on the spec. There's something both beautiful and insane about the situation, which persists to this day.
I just checked the prices for the cheap Arduino Pro Micro boards that used to be around $1.40 or so just a few years ago. They are >$5 now when buying from AliExpress and >10€ when buying from ebay.de! The chip shortage is real.

Given the increased prices $0.70 for thie RP2040 seems like a good deal.
TinyBase lets you set up event handlers with arbitrary data granularity, making the data store reactive.
COM+ revisited