skysight-inc/HackerNews huggingface dataset:
How much old advice on Java concurrency will virtual threads change?

I'm building a course for people who are new to Java concurrency and I've made the assumption that from September, you will almost always _choose_ virtual threads over platform threads. The default virtual thread management surely matches what most people want most of the time (1 worker thread per CPU core, virtual threads on top). It removes a lot of the old worries about management of thread pools and how OS thread implementation details "leak" into Java.

It's brought it much closer to how I'd written coaching material for multithreading in Go, but the Executor abstractions will still let Java programmers shift over from platform threads at their own pace.
I've read that SFT is good for "leveraging existing knowledge" gained during initial pretraining, and helpful in changing the way that the model responds, but not useful for teaching it new knowledge. In your experience is that true?

For example, changing the way in which it responds could be:

- debate me
- brainstorm
- be sarcastic

Which also seems like something that could be accomplished with a system prompt or few shot examples, so I'm not sure when SFT is the more appropriate approach or what the tradeoffs are.

Alternatively, gaining new knowledge would be training it on a dataset of e.g. sports trivia to make it highly effective at answering those types of questions.

P.S. nice username... Irving Fisher would approve.
The Cult of Kubernetes (2019)
I dunno, I am pretty sure I got Java readability the second month I was at Google and was already in the OWNERS file.

I was a readability reviewer and most of the readability CLs were the first project a person worked on at Google, often rather unnecessary but redone strictly to meet readability requirements (largely new code, more than X lines, etc.). I would go back and forth for quite a while to turn 1000 careless lines of throwaway code into 50 lines that were actually good, but I basically had to grant readability after that one interaction, and it never felt great to me.

The most hated readability process at Google was Go's process (at least in the early days; k8s is obviously not using it), but I think it was actually one of the best. It took me a long time to get Go readability, but after going through the process I feel like I'd write the same Go code as anyone on the Go team. When I look at people's open source projects I think to myself "don't they know that that Simply Isn't Done?" But of course they don't; Go readability can only be experienced, not explained. People didn't like that process, and I am sure I said nasty things about it at the time, but in retrospect I really like it.
My vote is for x32.

(you didn't know? https://wiki.debian.org/X32Port)
See "Can I delete my account?" - https://news.ycombinator.com/newsfaq.html
> Nobody should be writing code with the goal of passing a code review.

It's not backwards. Code needs to be readable, well thought out, bug free. Code review (done well) helps establish these points.

> If you're writing a system that requires 5000 lines of code, it's a waste of your time to figure out how to break it up into 5 or 10 PRs

I guess if you think those 5000 lines are perfect that makes sense. Often big PRs in my experience have a lot of issues that the authors and other reviewers will have trouble catching.

> Once they've demonstrated their ability to write good code, from that point forward you trust them not to screw things up.

Ha! I don't even trust myself not to screw things up.
It's really weird to me to see people rail against companies releasing what is essentially open source and then reserving the right to charge for hosting it.

It was even weirder to see hordes of people rally behind Amazon's moral crusade against it.

It's all rather reminiscent of Google's anti AGPL tantrum (e.g. like when they banned it from their code hosting platform).
They should just quit altogether, and leave only people who can't get a new job working for Grindr.
> It was called AMD64 when AMD and Microsoft designed it,

The original name was x86-64. Quoting myself (https://news.ycombinator.com/item?id=36075840):

> I still shake my head at how they were able to successfully rebrand it from amd64 to x86-64

It's the opposite: the original name was x86-64, and amd64 is a later rebranding. See, for instance, the original web site for this (then) new architecture: https://web.archive.org/web/20000829042251/http://www.x86-64...
torch-grammar generates a mask per PDA stack... we don't try to compute all the possible stacks. I'm sure there's something smarter that could be done here and you've probably figured it out (though IIRC regular languages don't have the arbitrarily recursive stack problem that you get when you get to context-free languages?) anyway, in practice we spend a few milliseconds on the first few requests building caches and then just apply masks from caches after that.
XML Elements themselves: their naming, their attributes, comments, indentation. There's more opportunity at every level of the hierarchy to demarkate and establish meaning. Having closing-tags as well, I've found, is a massive boon; LLMs can better understand what "finishing" looks like if its delimited in a semantic way - with a name.
Partition them by velocity
Cool app.

Wonder if you can potentially use a combination of Llama2 and GPT - to save costs on using the OpenAI API.
The sibling comments here are weird to me. IME the primary reason to us GraphQL is explicitly solve the dilemma of "ReST-ful" endpoints:

1) An endpoint returns a superset of the data any client may need, which means more data is loaded than any given client needs (which means wasted bandwidth/compute)

2) An endpoint returns a subset of the data all clients need, which means any given client has to tack on additional queries to get everything it needs (which means more roundtrips)

(There's the third option of tacking on "includes" or "excludes" parameters to endpoints, but at that point you're evolving an ad hoc, informally-specified, bug-ridden implementation of half of GraphQL, to massacre Greenspun's tenth rule).

How important solving this dilemma is to your application may be a function of your team or system topology, and the type safety that GraphQL happens to come with is a nice bonus, but this dilemma is the crux of things.
2.3 billion people are already using IPv6. It's not ubiquitous, but it seems to be here and working just fine.
Manuel Bronstein wrote a book [1] about symbolic integration, but unfortunately it only covers the transcendental part. There is also a shorter "tutorial" from some workshop [2].

[1] Manuel Bronstein: Symbolic Integration I, https://doi.org/10.1007/b138171

[2] https://www-sop.inria.fr/cafe/Manuel.Bronstein/publications/...
I would love to know this too. For me it’s involved too much manual copy-pasting of existing code for context, for it to feel like it’s doing much for me.
They do, but it's a form of imitation, not actually knowing what they don't know.

Ask an LLM to imitate a confident physicist and it will try, regardless of how much physics it knows.

Or if you tell ChatGPT that it's wrong multiple times, it may learn the pattern and assume it's always wrong, resulting in a downward spiral. (This can happen when using Code Interpreter and it makes several failed attempts to correct a mistake.)

The difficult research problem is training it to have an accurate model of what it knows.
You get a few layers for free by using Spring alone
I'd love to understand this too - my experience has been that I can generally write what I want faster than figuring out what prompt will get something close to right, and then editing/revising it to make it right.

Add to this the limited usefulness for generating code that's contextual - making some method deep inside a component tree that needs to reference a service class, and pick some dom elements to mutate etc... it requires knowledge and reasoning about the project and overall code structure.

I don't understand how folks are using it as a productivity booster, unless maybe as something like a better StackOverflow?
> "free", but you often get what you pay for.

You pay your taxes and you gets your health care.

As opposed to the US where even if you pay your premiums you may not get coverage if you go to the "wrong" (out of network) hospital, or the "wrong" (OON) doctor even if in the right hospital. Be sure to inform your ambulance driver of your in-network hospitals so you get taken to the "correct" hospital after a car crash.

When my father had to get new heart valves the most that had to be paid was hospital parking.

source: am canadian.
This is actually a serious proposal for the Rust language, it's called contexts and capabilities

Here's a blog post from 2021 https://tmandry.gitlab.io/blog/posts/2021-12-21-context-capa...

This isn't implemented yet, and the proposal never matured into a proper RFC, but there's high interest for some solution along those lines
Mainly because in 2019 I was offered an opportunity to be the "tech guy" for a small startup and you know how those go. Since I was alone it just became a DevOps/dev/helpdesk role over time.
Honest answer is mostly that I forgot; there was one more small TODO that I needed to fix before I wanted to publish it, and then I got busy and forgot about it.
Japan has private property, but the Japanese stock market has been going sideways for years.
Beside legacy code, in what context would you start a new project
un java?
> Unfortunately whoever ported it was brand-new to programming or something because they pinned the game speed to the CPU speed, or screen refresh rate or similar.

'twas common practice than you might think--
https://www.vogonswiki.com/index.php/List_of_CPU_speed_sensi...
http://www.cpukiller.com/
The implied correlation and statistics here feels suspicious. Can they also say “we have seen people bounce back from early signs of dementia after getting eyeglasses” ?
Check out Tokyo. Most streets have no sidewalks. Very walkable.
What they should propose is a 10 year fixed rate that PG&E will buy the power back for... to secure investment in the technology.
Despite being the largest state there's not a ton of room in the biggest metro areas for new housing - people are already packed like sardines between foothills, and going up into them is just begging for destruction due to wildfire.
Imagine doing this in a country where there are actual labor laws like France.
The Grief over the use of x64 for AMD64 or X86-64 is based in the prior use of "x64" for the DEC Alpha architecture in the hardware naming: "DECchip 21x64" [0]

Digital was earlier to market the Alpha as a 64 bit ISA than either Intel's Itanium ( IA-64) or AMD's x86-64 which is also called AMD64 [1]

[0] https://en.wikipedia.org/wiki/DEC_Alpha

[1] https://en.wikipedia.org/wiki/64-bit_computing
You're right, of course. What the OP was suggesting has been tried many times before. They were called "the projects".
I'm not saying they can't afford high wages. I'm saying levels.fyi-scale wages for a few years in a normal housing market would leave an employee much pickier about companies/projects/conditions vs. someone who still needs to grind hard for his first 1BR in New York or San Francisco.
The problem is that reviewing is itself a skill, and many people are bad at it.
I emailed the contact person:

Hi,

OpenFarm has not been maintained or worked on in several years and the Slack group is no longer active. If you are interested in taking on a project maintainer role for OpenFarm, please get in touch through the OpenFarm GitHub repo! And please note, this email address is no longer checked regularly (this is a vacation responder replying to you). Thank you for your understanding.
Thanks for the explanation. I guess the overhead does make sense at a certain scale. The unfortunate thing is that articles like this always end up inspiring some bored engineer/CTO to redesign everything so it is "webscale" like Netflix and blow the mid/small-sized companies' Christmas bonus on AWS bills.
Might also want to try an psychologist. The person you go to often suggests solutions that they're familiar with. Meaning, if they often cure things with drugs they'll likely give you such a solution.

You didn't really specify the problem. Sometimes it could just be the brain. E.g. sleeping issues occurs more often with ASS. So see various types of specialists so that you're not stuck to the things a specialists knows about. Might be that another specialist more easily can spot your issue.
I use ChatGPT (with the paid GPT-4 model) for certain things when I'm stuck. I use it to explain/rephrase concepts that I'm confused about. I occasionally generate some anonymized stuff like short code snippets, devops configs, boilerplate, and tests.

Are people using it to pump out full apps and services or what? Anytime I've tried that the result quality is poor, even after lengthy explanations of what I'm asking it to build. Sure, sometimes it saves a little bit of time, but sometimes it also wastes my time by giving me nonsense or never zoning in on what I'm asking for. I don't see how people are becoming so much more "productive" with this, unless they're mostly talking about stuff like non-code written content.

It doesn't help that my company's infosec policies forbid putting any proprietary data or code into these AI tools, hence why I only ever ask for short snippets.
I can imagine how the conversation went with the enterprise customers:
"Where does this send the data our employees enter?"
"Same place as if they used the free ChatGPT chat bot..."
== was already a silly operator, === is just ridiculous.
Which are both fine?
Good example. Tillman does not prohibit most PACs.
I just add a "cancel X trial" event to my calendar and then don't have to worry about forgetting it.
Honestly, I see this happening. Even if the "hack" is as simple as strategically placed traffic cones :)
Title is incorrect.

Two weeks to decide if they can move, with RTO work starting in October.

Still bad, but not terrible.
Does your PhD require increased reaction time?
Roles are cross functional. You can have ApplicationUser, AllowedDebug, Network1User, PythonDeveloper, Database1Developer, etc. etc.
They did some stubbing as needed, but that doesn't change how it's still messy and tedious for the backend team to support so many different combinations of data instead of just handing them a GQL.

Also, to be frank, frontend team was paid a lot less per head than backend team. Their expertise was just in building the UI according to what the backend team and designers gave them, and they were very good at that. Stubbing wasn't an efficient use of their time.
A get request can leak data via the request path or querystring parameters, if that was restricted you could setup communication which time or frequency imply activity with a morse code like protocol (and with enough requests, easily transfer megabytes of data).
The article I linked has much more information on the concept but essentially Apollo and most other GraphQL clients/servers don't do fragment stitching. Imagine laying out the data dependencies for each of your Vue components and having the frontend automatically refetch or cache invalidate whenever the data changes, with no input on your part. You would thus never over or underfetch your data, you get exactly the data you need at any part of your application. This is what Relay does.

Relay is for React only however since Facebook made all of these technologies. I recommend using React and NextJS if you can, I used to use Vue but found that the ecosystem for non-React frameworks was still worse than React, so I switched.
I really hope OpenAI add something like this to their endpoints soon.

Being able to pass up some kind of grammar (a regular expression, or a JSON schema, or some other format) and have this trick run during their token sampling process to ensure the output was compliant would be incredibly useful.
And just a note, this is called Reader monad in Haskell

In other words, receiving an implicit parameter is a kind of effect. So another way to provide this feature is to have a full blown effect system (which is much more general and is probably overkill, but there's also some interest for that)
> How/where? Is this actually a 'solid insurance is hard to get problem'?

Insurance can be contingent on different things:

> Where can I receive care?

> If a provider is not in a plan’s network, the insurance company may not pay for the service(s) provided or may pay a smaller portion than it would for in-network care. This means the enrollee who goes outside of the network for care may be required to pay a much higher share of the cost. This is an important concept to understand, especially if you are not originally from the local Stanford area.

* https://vaden.stanford.edu/insurance-referral-office/health-...

If you happen to be in a car crash, make sure your ambulance drive takes you to an in-network hospital.
Whether security issues from a disgruntled employee, or from the fact that good employees quit because they can find better terms at a different job - probably time for me to delete those ass pics.
Personal story from ex-Googler: after getting exasperated at yet one more internal tool launched with great fanfare and almost no testing, let alone documentation, I suggested to the Internal Tools group that we have a contest for BEST internal tool.

Not "worst" since that would be too hurtful. The hope was to recognize excellence, motivate people to be better, and maybe shame the people whose tools received no votes. This suggestion was summarily dismissed.

There were, indeed, some truly excellent tools: Dremel comes to mind. And lots of tools that were nearly unusable.
Good to know about the sales, though being in Canada might hamper me there. The refurb and edu discounts are pretty decent though, and I'd probably consider those if I really start pursuing an upgrade.

HDMI has always been a bit irrelevant for me, aside from using it with work-issued displays. I've always used displayport over thunderbolt, and don't know that HDMI offers any advantages. I'd prefer almost any other port over HDMI.

My issue is more that every time I spec out a new MBP, it genuinely feels like I'm being grifted, and it really turns me off more than in the previous 10+ years I've been buying macs. $200 for a ram upgrade was already too high, and hurt the wallet then, but $500 - $1500 CAD for ram upgrades (inflated by the apparent, probably artificial, requirement to choose CPU upgrades that I'd never have in the past and wouldn't likely get any value from.

If I choose the minimum CPU that allows 64gb, I then need to spend an addition $750 to add 8 gpu cores and go up to 96gb (not that I'd necessarily go that high or feel like I'd need to, but it's not like I can upgrade, and just stands to illustrate the point). $750 is my damn rent payment.

So before even going past 512gb ssd or including Applecare or taxes, the computer sits at $5100 CAD, if I were to max out the ram, on the 14" new.
Thank you. I'll see what I can do. If I can't, well, I did something wrong.
Backticks are used as literals in a lot of contexts, especially DBs.

Overloading that behavior by default would likely blow up a lot of code and certainly violate the principle of least surprise.
this is indeed what had happened to one of my top listens in 2022.

artist decided to revise their own back catalog narrative so to speak, and I get it but holy crap the horses already left the stable.

So it is not for sale. I might find it on soulseek (thanks for the suggestion someone else ITT). the album meant a lot to me, as these things can when they're literally top playcounts for the year - clearly it does.

and it was, you know... super-indie, mom's basement kind of soundcloud & distrokid released production.

wonderful and now gone. Had I bought this on iTunes it would have gone into my offline library. it was for sale, and is no more.

my takeaway has been to get very defensive about any hyper-indie releases that I want to hang onto.
You know the ones I'm talking about. The true believers.
As mentioned in the video, this is caused by a 12k cyclic process happening on Earth as well as the whole Solar system. Please watch it as a whole for more details and references to further sources. This information is simply invaluable.
Given how you've been able to do this, I'm interested to hear your thoughts on Apple removing support for 32-bit code?
Homemade WRX-Powered Classic Mini Is a Mid-Engine, RWD Go-Kart
You’re still refusing to address my questions. Why?

Why do I owe you the results of a pretty simple Google search, which we both know you only want so you can poke holes in one or two examples and pretend that invalidates the lot, while you won’t address the very simple questions I initially asked you? Are you embarrassed?
*12k year cyclic process
Correct. if you don't defend your trademark then you risk losing it.
Layoff without calling it a layoff.
More like "ynab terms and conditions are crap and when I asked questions they ignored me instead of engaging".
I would still pick Java any day over the vast majority of languages. Gigantic ecosystem, gigantic community, gigantic knowledge base, solid IDEs, and the list goes on.
No autoproperties yet?
I still have the bound, page-numbered notebook issued to me by Microsoft in the late 90s for this exact purpose, along with a lecture explaining the methodology above. (A rather misguided effort by an IP attorney who was apparently new to software…)
Looks very interesting
When your engineering team is experienced and proficient in Java and your organization has built substantial tooling to support it.
High performance, typesafe code that can be maintained by a large team. Also has a very well established ecosystem of libraries, and multiple languages to choose from (Java, Scala, Kotlin, Clojure, etc)
The solution to that is not to abolish landlords, it’s to tax land ownership.
Farmers, construction, etc are required to keep their non-taxed vehicles off the road, if they're caught on the road with them they can be required to pay any taxes on the entirety of the odometer since the last sale.

The cross-state-borders could simply require you to report your odometer readings on exit and entry to the state. I don't think it's unreasonable to say that the majority of drivers would not care about a few dollars "extra" from some cross-state adventures, and those that do care can do the extra couple of minutes of working.

Another alternative would be to require all car chargers (including those connected to personal solar) include meters internally and require the owners to pay taxes on those (which would be trivially integrated with pricing on commercial chargers, but there are plenty of non-commercial deployments).
Oh, they also don't give a damn whatsoever. But they have to pretend that they do to a lot more than Wall Street does. They still have end-user customers, who have the power to buy goods and services, which in turn does have some pull, albeit not much.

If Apple buys Disney, and a bunch of people leave or join Apple TV+ due to said acquisition, that will affect Apple's stock, and you can be sure Wall Street cares about that.
I just hope this furthers V2L adoption

I would argue that would furthers more V2L adoption is more blackouts. It's one of the reasons I'm selling our Honda generator: have a Hyundai Ioniq 5, what do I need a 2000W generator for? What did I ever need the Honda for? Blackouts.
Michael Burry shorts Major index in sizable bets