Hacker Newsnew | past | comments | ask | show | jobs | submit | buildbot's commentslogin

This would be such a good game for introducing students to digital technology! This is so fun! We just had to draw them by hand back in the dark ages of the 2010s.

Thx, way better (imo) than just reading slides or (god forbid) pure text describing comp arch

100% agree - the way that you have the very subtle arrows on the transistor drains that show the actual current flow is really smart too. I struggled with visualizing the current flow in undergrad for an embarrassingly long time.

Block signed a friend of mine, they quit their other job, then block was like whoops layoffs including people like this person who hadn’t even started. Super unethical.

I’ve been in IT for 25 years, it has happened to me once, unfortunately it isn’t that uncommon.

In the USA at least sure. This was in a country with lightly better employment protections so it’s quite uncommon.

Counterintuitively, systems with heavier employment protections can make it more common to cut recent hires.

Employment protections usually come with a probationary period before they kick in, so employers can remove bad hires early. This creates an incentive to remove new hires before their probationary period is up if they're showing any signs they might not be the best candidate for the job.

Even when new hires are good and the company wants to keep them, heavy employment protections favor longer term employees. If the business environment changes and they need to reduce headcount their hands may be tied in ways that require cutting the new hires before the tenured employees. This happens a lot in labor unions, too, where tenured employees have greater standing than new hires when push comes to shove and someone needs to go, regardless of performance.


If your system is setup that way you likely have a better social safety net too?

And this person was removed before any probationary period, before they started, without cause.

Laying off employees by seniority is not the same level in my opinion.


In Germany we have pretty good employment protections (I think at least!), but this would be legal too. You have a 3 month grace period where the employer can terminate the contract without giving much reason - you gotta survive this period then the protections kick in and they can’t just terminate the contract without a justification and notice period. It sucks but I think in this case even the best protections won’t help much.

It's usually 6 months probation in Germany, not 3 months

Only 3 months? I had 7 months in France.

That's so messed up. I hope they're doing ok.

They are taking it in stride at least!

Why did they even hire if they had to just fire a person who hadn't even started. It really reflects to the level of incompetence within the company.

I am sorry for your friend, I hope that he is doing fine, Is there anything that they can legally do for this to block?


They are doing okay! And there is some legal actions possible, though not worth it in this case.

Not the only scam on eBay these days - https://news.ycombinator.com/item?id=47566523

Empire earth slapped so hard. Both 1 and 2. Honestly now that I’m thinking about it, going to set aside some time this weekend and play it again!

Alpine & Linux?

FYI Alpine: https://github.com/realpine/alpine Not Alpine Linux, too late to edit to clarify

Most probably it can’t connect to the server without running IT-mandated security software that runs only on Windows

Are you running that on a flight system or on an additional computer where it would be fine to run Windows?

The entire point is to avoid an OS like windows; and an email client like Outlook?

Yeah I get the point, I'm saying it's not really a good point, running Windows and Outlook on a secondary system is fine. Forcing the astronauts to learn to use some other system would be a waste of time and probably worse than whatever it is you see as the problem.

It’s a community project supported and sponsored by AMD according to their GitHub; https://github.com/lemonade-sdk/lemonade

AMD employees work on it/have been making blog posts about it for a bit.


Random chance has a really good sense of humor!

Takeout always fails for me, with ~11TB of data in Google Drive.

Why would you use takeout to download Google Drive contents when syncing to your local computer is its entire purpose?

Because the Google drive desktop app crashes as well :)

That is odd I can't remember it ever crashing on me.

I long ago used arq backup with google drive as a target, and there’s something like 1-10 million little chunk files in that directory so it’s probably that…

Google Drive files you can sync to local disk via the Windows or Mac app.

Fails!

Then your data is gone.

There’s like 100 comments blaming raycast, they should just sue for damages lol.

Had I not seen this thread, I would have assumed they consented to it, and I'd never willingly interact with Raycast or it's team in any way. I still have a somewhat negative opinion, so I think it's safe to say there are damages.

As a data point, I consent to be counted as associating raycast with the Microsoft brand and viewing them negatively as a consequence of using pull requests as an advertising canvas.

They should sue to have the ads removed from the texts they were inserted into, which is a vastly more difficult problem than simply paying some dollars.

Naively as a West Coast Verilog person, VHDL Delta cycles seem like a nice idea, but not what actual circuits are doing by default. The beauty and the terror of Verilog is the complete, unconstrained parallel nature of it’s default - it all evaluates at t=0 by default, until you add clocks and state via registers. VHDL seems easy to create latches and other abominations too easily. (I am probably wrong at least partially.)

((Shai-Hulud Desires the Verilog))


AFAIK, creating latches is just as easy in Verilog as in VHDL. They use the same model to determine when to create one.

But with a solid design flow (which should include linting tools like Spyglass for both VHDL and Verilog), it’s not a major concern.


SystemVerilog basically fixes this with always_comb vs always_latch.

There's no major implementation which doesn't handle warning or even failing the flow on accidental latch logic inside an always_comb.


(System)Verilog has delta cycles too you know, they call it an event queue, but it's basically the same. It's the direct variable updates that happen outside of this mechanism that cause all the issues. Imho it was a poor attempt at simulation optimization, and now you can't take it out of the language anymore.

I did not know!

[flagged]


> Once the design gets past toy size,

Do you consider 800+mm2 slabs of 3nm of silicon still toy size? Because there's a very high chance that those were written in Verilog, and I've never had to chase sim vs synthesis mismatches.

> Verilog gives you enough rope.

Yes. If you don't know what you're doing and don't follow the industry standard practises.


That does sound like my experience…

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: