skysight-inc/HackerNews huggingface dataset:
Huh, that seems weird to me. _Obviously_ push would go almost nowhere in 5 years. Hell, HTTP/2 itself is still extremely new. Server push requires people to totally redesign how their infrastructure works, because their web server needs knowledge about the application.

I would expect server push to be basically unused until something comes around to automate it. It seems totally plausible to me, for example, that NGINX might add some logic to automatically keep track of which resources are requested after which other resources, and, for example, notice that "/style.css" is requested after "/" 99.9% of the time, and therefore automatically push the stylesheet.

It says a lot about Google if their approach to this stuff is to build something which requires the entire world of web servers to adapt, and then rip out the feature if it doesn't take off right away. If they were serious about it, getting everyone to restructure how their infrastructure works should've been treated as a decades-long project.

This just reinforces my existing view of not trusting Google for anything important. They just can't keep at a project. Imagine being the sucker who suggested that a business should spend a load of time restructuring their back-end infrastructure to support server push, just for Google to rip it out.
Unused Mainframe Linguistics
> 3. Steals a web session, cached password or authentication token, resulting in compromise of employee credentials to be used elsewhere (e.g. reused to access enterprise VPN).

How do you do this without a browser vulnerability (and assuming it's not also XSS/CSRF like the previous point)?
why would a company pay and offshored resource the same as localy?

Sounds like you want to have your cake and eat it
This is the real answer. The effects of UML will live on forever, but a formal language for it has been dead for a long time in common use, though some of course will still use the exact formality.

The value of UMLish things is just visually diagramming data and systems. Boxes with arrows and some data inside is typically enough to do the trick. Lucidchart is thriving despite many not actually writing explicit UML on it.
I don't think it'll die entirely anytime soon, but certainly it has lost in mind-share - especially in the fully by-the-book way. Vaguely UML-like adhoc notations are way more common, and will survive even longer. (And my interactions with people aiming to do it properly have involved more ambiguity than would expect from a good standard)
Unified Modeling Language: https://en.wikipedia.org/wiki/Unified_Modeling_Language
It's pretty sad how bad both iOS and Android development ecosystems are. Xcode is crap, homebrew is crap, gradle is crap ... Basically all tools hate automation. SPM seems like thing that could make things better, but it's swift only. Also the build times are ridiculous. How I wish I could just run compiler on a text file and run the god damn program I wrote on the device I own, like on every other sane OS.
> It's not clear to me why the federal government should accommodate the state taxation structures.

There is potentially an argument for no SALT deduction, though I think a lot of factors (including federalism) weigh in favor of it, and that it is on-balance justified; its something on which there is reasonable disagreement.

But that’s not the debate. The debate is between a limited SALT deduction designed to create federal pressure to force the more successful states to adopt tax and spending policies more like the least successful states, and an unlimited SALT deduction that lifts the federal governments thumb off state tax policy.
Smae reason there aren't more efforts to make more men into cleaning or nursing. The point of inclusion efforts is to help people who want to do a job they are qualified for, but are prevented from doing by discrimination.
Without making a research project out of it:

- Rome to Athens

- Paris to Barcelona

- Madrid to Stockholm

Much of Europe is a very far way from having a seamless integrated cross-border train system.
But with a book, you have that privilege in perpetuity, and you can loan, transfer, and resell it.

Coincidentally, NFT’s got the “transfer” side of the equation, but forgot about the “privilege” part! The tokens are yours in perpetuity, and can be transferred to others, but it’s not at all clear what privilege they provide.
Like actual UML or UML-ish diagrams?
Lisp and Scheme graphical debuggers do just fine tracking them.
Pointing out what you see as bad regulation, doesn’t imply that all regulation is inherently bad, or that less regulation is inherently good.

Well, this is a post about Bayesian inference, so technically pointing out bad regulation should cause people to update their beliefs by adjusting the prior probability that any new piece of regulation will be bad. Assuming people reason based on experience of course, which is reasonable.

What we have here is an unclear and highly controversial problem that many people would argue doesn't even exist at all (I don't see anyone in my own life who has been harmed by AI for example), a very vague and poorly worded regulation, which nonetheless has massive fines attached to it. That makes it pretty much a textbook example of bad regulation. And unfortunately this is the latest in a series of such anti-technology regulations from the EU, which doesn't seem to be learning how to write higher quality regulation or how to judge proportionality.
Refunds aren't sufficient, you are owed whatever the replacement cost is.

If the good is no longer available except for at 10x or 100x the price, you are owed that. If the good is no longer available at any price, but the person with the liability is capable of making it available, they should be required to do so (or negotiate a contract with you that buys out your rights, but you should be free to decline that or to set whatever price you want).

This is especially relevant in the digital realm where it's an especially effective tactic to undercharge to try and starve competitors, and then raise prices.
The lemon-game bit at the end is correct. If you don't say what you want to pay people, they assume you don't want to pay them much, or that you don't want to tell your existing employees. So then the good people decide not to apply, and it takes longer to find someone.

There's a similar game theoretical game for the employee. You don't want to ask immediately because you'll seem greedy. But you also don't want to waste a bunch of time doing interviews and homework, only to find a booby prize at the end. So as long as there's enough firms that do publish a range, you're going to apply to them.
Not just side projects. We did two feature animations using Blender, more projects in the pipeline:
https://m.youtube.com/watch?v=iZn3kCsw5D8
I am pretty sure I saw the demo running in my browser for this, the link was at the end of one of the talks I think. Will post here if I find it
Wikipedia has a pretty good article on the banana issue: https://en.wikipedia.org/wiki/Commission_Regulation_(EC)_No....
Running the train up the central valley was always part of the plan and is a perfectly reasonable thing to do. The problem is that California is currently building a train from one end of the valley to the other that _doesn't_ actually connect to either major metro area.
So-called hard science fiction writers do not seem to make more plausible predictions about the future. It's not clear they are even trying to, since plausibility doesn't necessarily mean entertaining. The so called hard science fiction writer just throws some references to math or physics among the implausible world building.
These things all still exist in some capacity, though obviously it has become more efficient. Bandwidth isn't free, for instance.

The cost of publishing hasn't changed much. It just shifted from "making it to the limited selection" to "being visible in the essentially limitless selection". In the end you still need to make deals with retailers and invest into advertising (especially when storefronts don't do deals - or at least say they don't, hi spotify).
I mean, you're free to buy or not buy whatever ideas you want.

But it's not really arguable at this point that women and people of color (especially black & indigenous) are treated less well, assumed to do a poorer job, and generally at a disadvantage when negotiating salaries.

(This all completely aside from the fact that "good negotiation skills" should not be the reason Employee A gets a better salary than Employee B, unless the job itself is significantly about negotiation.)
Also I don't think there ever were physical audio formats with DRM? CD came out way before piracy was anyone's concern, and then it was too late to change anything.

On the other hand, all digital video formats have always had the technical capability for DRM, starting with DVD.
What's the harm to person B of person A getting to know person B's salary?

In a more general sense, more information makes for better decisions.
That's what I tend to see as well. Used around documentation and drawings. Used much less in any context around real code...little code->uml, and almost no uml->code.
That’s how I think of it too. It’s more like pseudo code for throwaway diagrams, not living documentation.
GitLab supported Mermaid.js rendering for a while but last I checked that was broken.
That showed the most promise for a practical use of UML.

I have no idea what that article is trying to get at about multi-dimensional diagrams.
I can make masala in UML, there's literally nothing stopping me.
Looks like an interstate network to me, not commuter rail.
UML suffers from false precision. Nobody cares about most of the specific rules and grammar of the language because the output is designed to be generally readable by a lay audience. The time your spend making your diagram compliant with UML is better spent making and remaking good general diagrams.
Some studies suggest happiness per dollar salary peaks around $65k to $90k USD. So for an international corporation where obviously most people will have cheaper cost of living than the United States, that seems a good starting point. This is low for Silicon Valley salaries so it may dissuade those accommodated to salaries in that high range.
Or DirectX. Mostly, I think the expectation is that folks won't handwrite vulkan, they'll use a higherlevel API, like a game engine's API.
I agree that job descriptions should show a salary range. Otherwise you don't know if you should even apply. I also think that we all need to learn to estimate our market value and negotiate our salary, no matter what gender or race.
> There are no AI papers I recall that discuss how to build a mind controlling AI, let alone one that's designed to cause people psychological harm.

https://www.pnas.org/content/111/24/8788.full

"Experimental evidence of massive-scale emotional contagion through social networks"

"Core Data Science Team, Facebook, Inc., Menlo Park, CA 94025; and Departments of Communication and Information Science, Cornell University, Ithaca, NY 14853"
I went with your suggestion but changed a little I think I made it worse
Why wouldn't they be able to work at the same time? People adjust their schedules for work when necessary. I work the standard 9-5 nowadays, but several years ago I worked at a warehouse from 6pm - 4am. I slept from 5am to 1pm as a result. Sure, there are outside pressures, like family obligations, but the job usually trumps all schedule conflicts in my experience
It's not popular because it's not realistic in most environments. In many cases it's advantageous to use those things you listed because that's what the market can provide talent-wise. I'd rather deal with learning new tech that's well documented than some custom lib that "just works" but no one understands because the architect left years ago. My whole career has been about consistent education, so that doesn't intimidate me. Working on undocumented architectures that I have to make substantial changes to (and not knowing all of the side effects) is what intimidates me.

Turnover is a reality that can't be ignored. New people come in and now have to figure out something that reads like a stream of conscience. It isn't well documented, doesn't follow the latest best practices and doesn't support modern paradigms and uses outdated frameworks/libs, but works great.

The apps I build always take into consideration the talent pool my employer intends to pull from. The reality is that they (usually) can't hire general "technologists" that are proficient at all layers of the stack. If the project is something that only you will ever work on, then you can do whatever you want and this whole conversation is moot.
There's a negotiation involved, once you decide you want to offer the job to someone. They might think they are less likely to get the job if they ask early, yet they might also not want to go through the whole interview process to find that your range is too low for them.
That is picking on the details.

I think most of people were doing UML-ish diagrams anyway because unless you really have a use case for it it is just wasting time to go full "UML".
I mostly use it to understand code-bases.

It's a bit unwieldy, because of its OOP origins, but it helps me to visualize how code relates to other code and how software behaves at runtime.
A thing I never understood is, what happens if, let's say, I stay in a HCOL area until I am doing interviews (eg Switzerland) and then when hired I move back instantly to a LCOL area (eg Albania): what happens now to my salary? Do I get a cut just because I decided to move?

And what if I am a digital nomad and know I want to change nation in which I stay every x months?
Blender has been converging more towards industry standard UX practices, while GIMP sticks to its tried and true idiosyncratic way of doing things. It’s good GIMP exists, but it’s a failure in the sense of that it remains a programmers idea of what an UI should be. GIMP could have a had a lot more uptake if it wasn’t so stubborn. Something the folks at Blender understood at some point.

Management of Blender by Ton Roosendaal has been really good.
I'd rather suggest that people learn D3D11 first, if they can, instead of Vulkan. The OpenGL programming model has a lot of backwards ideas that can make graphics seem far more complicated than it is. Vulkan removes those and gets closer to the D3D11 style, but it also introduces a lot of more complicated ideas. Learning the whole gamut at once is a challenge.

There are other options to get started with graphics. Frameworks you can use to start putting your toes in the water: any game engine, a higher-level graphics framework like raylib or bgfx, or a cross-platform graphics layer like WebGPU/wgpu.

I don't want to gatekeep, just being realistic that if you're new to graphics in general, Vulkan might not be the best place to start. You'll get there eventually though.
Yeah I'm not sure how to drive it either. I'd like to use any sp32 but that only has like 40 gpios max. I think you can set up logic gates or something I don't even know what that means except very superficially superficially I'll cross that bridge when I get there
I think this is somewhat reductive, as it make a few blanket assumptions that I don't think can be assumed.

The first is that better candidates will get the maximum salary out of a company, and less qualified candidates will get less. This seems to indicate that people who are qualified for a given job will also be excellent at negotiating for it. I don't think these two skills are in any way related.

The second assumption I see in this is that candidates should "women/bipoc can't navigate this system." I think what you're missing (and the article states this) is that minority candidates will be looked at differently when asking for money. There's also the difficulty of determining one's worth, especially when companies don't post average salaries. It can be a difficult guessing game to even ballpark what your value is (even with companies like Glassdoor posting salaries), and if you made less money in your previous job, you're likely to ask for less again. This naturally disadvantages minority and female candidates that have made less historically.

Yes, white men aren't born being able to navigate it. But this ignores the fact that our society is set up to encourage confidence in straight white men and discourage it in many other groups.

In addition, posting a salary range has many positive downstream effects as mentioned in the article. My brother recently benefited from this, as his company posted a job listing for a similar position to his with a starting salary of 20,000 dollars more. He was able to use this to advocate for higher pay.

Bottom line, posting a salary range just adds transparency to the process and evens the playing field a bit. Needing negotiation skills to even get in the ballpark of your true value is crazy; even car companies give you a price point to start from.
Many years ago there was a VT-100 terminal program called VT-10-Squared for the Atari 8 bit computers that managed to produce legible characters that were only 3 pixels wide.

IIRC, it had both upper and lower case, as well as the special VT-100 graphics characters. It was definitely usable, if somewhat headache-inducing when used to consume many screens of text.

It worked by drawing the characters in "high resolution" graphics mode (320x192! Woohoo!) so you could use mainframe software on the Atari, which normally only supported 40 columns of text.

Looks like the software is still hanging around the various Atari archives... it might be worth extracting the font, if licensing permits.
New spherical flexure joint designs
Covid zealots say #believeTheSciene but the use the news media as scientific sources.

Post an actual link to ICU numbers if you truly '#believeTheScience'

Here I did it for you.

https://www.arcgis.com/apps/MapSeries/index.html?appid=078a3...

Do your own data analysis and see ICU admissions are only up 15% or so.

Also, according to other media outlets, ICUs in Toronto haven't filled up, they're 'NEAR capacity'.....which has been the story for over a year everywhere.

The media drums things up to make money and should not be used as evidence for your argument.

The media also said San Diego ICUs and Houston ICUs were overflowing but it didn't happen.

For example, this sensation article never happened:

https://www.google.com/amp/s/www.nbcsandiego.com/news/local/...

Do you have anything supporting your argument of hospital overflow with substance?

Or do you get all of your 'science' from the news media?
Thank you for that phrase.
Same here. I still think UML is a great tool, but few have the need to follow the standard to the letter. Often I don’t fully understand a problem before poking at it for a while.

As I write this I can’t help wonder if perhaps it would be useful to return to UML after doing some exploration and before starting the real implemention. Still everyone on a project would need a refresh on UML, most of us forgot most of the details.
I don't think the physical colocation is the key here.
What’s the harm to any person if private information of theirs is shared?

Person B should be (and is) free to tell person A their salary iff they want. If they don’t want to share that private information with A, no else should either.
Well, I was hinting at smaller digital storefronts! Many of them do offer DRM free digital books.

I can't comment on NFTs beyond "wow, what a wasteful scam".
Is the prospect of some hyperloop implementation impacted by this plan?
I can also highly recommend the UI library written by one of the authors, Tailwind UI. I got my first job writing a dashboard for a nonprofit about a year ago and I was sick of fiddling with CSS. $150 later I was flying through writing usable interfaces, plus they loved how it looked.
In my current situation I have the added benefit of being in a close time zone to our team which was in Belarus (who now are in Ukraine and Netherlands). I manage an 8-person devops team and act as liason to our backend and frontend dev teams, as wrll as manage the customer relationship.

Before this job I was an individual contributor getting 3-5 hours of overlap at a company distributed all over the USA.

This afforded me more than enough overlap, extra on-call coverage hours and a solid 4 hours of uninterrupted project time. It is actually a huhe benefit that I get that much uninterrupted project time.

Again, if a company sees value in my skillset and multiple decades of experience then they will have to pay me the salary I want. If not, another one will.

It has been at least a decade sincr I have spent more than 2 weeks per year in-office or worked in a team that wasn’t distributed over 4-10 time zones.
From your link:

> Support for Protobuf buffer serialization was a multi-year effort between Microsoft and Google engineers. Changes were spread across multiple repositories.

The implementation being discussed there is the main C# implementation from https://github.com/protocolbuffers/protobuf/tree/master/csha...
Renderman has been used by pretty much every VFX studio for the last 30 years [1]. I remember downloading and dabbling with it along with BMRT [2] in the early 2000s. It was the first widely used tool to have a procedural first approach to rendering.

[1] https://renderman.pixar.com/movies

[2] https://en.wikipedia.org/wiki/Blue_Moon_Rendering_Tools
Same here, UML was nice to create a visual flow of a project.
Never actually generated any code from the diagrams.
Luckily I have enough karma to afford these kinds of comments :-D

I never liked the arrow-direction in uml
This article references two different suits, and the headline is about the second one, but at least at the time I posted this comment, the part nearly everyone was commenting on was the first suit, with the "no reasonable person" line, which is the same suit as in the previous article.
Why is this sentiment so prevalent. I'm thinking more and more that simplistic and vague informal diagramming is a great source of confusion.

UML, specifically statecharts capture a lot of behaviour unambiguously, though it is hard to draw by hand (due to its hierarchical nesting possibility, so some kind collapse/expand system is required to draw them in a sane manner).
UML was propped up (and still is) by universities, but it was never big in practice.
Yep, I agree (I was short the stock). But the question is whether lying about FSD was a big part of the raise? I don't think it was, back then everyone assumed he was full of shit because he talked literal nonsense almost constantly (the number of topics on which he is a self-appointed expert is quite extraordinary). When the market cap is $1tn, that nonsense was behind the price.
Probably a bit like REST.

Seems obvious at first sight, then you get 80% right in 20% of the time, and don't bother to put in the last 80% of time to get to 100% understanding.
In theory, UML diagrams sound good. In practice, having to maintain them is PITA. I quickly abandoned them as soon as i went above 10 classes, which even a basic OOP codebase will exceed quite early on.
Only if they use DRM. It’s not possible for me to lose access to the music I’ve purchased on iTunes, the games I’ve purchased on GoG, or the audiobooks I’ve purchased on libro.fm. (Except through my own fault, which shouldn’t apply.)