dialamac

I don’t think so... the one local storage mentioned originally would not qualify as a backup.

That’s a very misleading headline. I got the impression this was something akin to VHDL or Verilog or SystemC in python. “Programming Hardware” the way it’s used here is pretty much the same as vanilla python, though I suppose a lot in this industry constantly need reminding of that.

Pharmacy, nursing, and medical students will find out soon enough.

Nope I get it and I think it’s absolute bunk. And while I grant others are entitled to their opinion I think the implicit dismissal of my (not uncommon) opinion is condescending. As pointed out RMS doesn’t support this idea, and while he’s not some absolute moral authority I’d say it’s a strong counter argument to some absolute consensus on a “spirit” of free or open source.

> I don't really get how people get this twisted.

Quite condescending this attitude.

I don’t agree with you at all, and find your argument completely stupid. I don’t think there is anything twisted about it. The software was released under license terms and as long as Amazon is complying with them there isn’t a problem, it’s really is that simple.

And really this is much ado about nothing. These fork fights are sometimes interesting with bit players, but the FAANGs of the world they could just build a tool like this from the ground up if necessary.

It happens temporarily all the time of course such that there are plenty of talented people underpaid at a given time but long term most will not be. I along with friends went through bouts of shitty jobs, but it is rare to stay that way. Hiring from the pool of low rate workers is not a suitable standard practice at a place that isn’t a shithole.. as we see here with Intel.

> The domain itself isn’t fundamentally unsafe

This makes no sense to me, what you’re saying here. You pass raw pointers to the Windows API for one, for which it makes no safety guarantees. Short of rewriting Windows from scratch I don’t see how this isn’t a fundamentally unsafe domain. Sure you could put more and more wrappers up on top (it’s not an even an issue of one-to-one translation, but how resources such as memory are wrapped), but whatever binding there is pretty much must be unsafe.

That it’s possible to write a safe wrapper is kind of obvious.

> Watching videos and doing general exercises ... may actually make them worse.

That’s what you said, and I stand by my paraphrased assessment. Essentially watching a workout tape is bad for you is what you said whether that is what was intended.

TIL on HN: doing a little bit of physical activity will make you deformed.

> Music instruction cannot possibly be effective without a visual component

I suppose blind people will never be successful with music.

Case in point was already mentioned. The New Yorker is the outlet that ran with the bullshit rent a family story.

CommScope Ruckus?

1 really doesn’t hold water. Some ISPs in the US still waive the fee if you don’t rent equipment, so that doesnt really strengthen the argument. I now have an ISP that doesn’t waive the fee but that doesn’t matter either, since it is not optional it is just part of the total sunk cost. I still use my own router.

Your whole argument doesn’t hold water because even with Comcast you can bring your own equipment. They don’t go out of their way to help you... but they don’t stop you either. Don’t see how that is “control”.

Maybe you will not call tech support when your own equipment fails but you clearly have no experience in a support role if you think other people won’t!

Just spend some time on GitHub issues for more popular open source projects to get an idea, and the multiply that by at least 10 for the general public.

Wikipedia has a pretty good explanation to your question how the memristor completes the quartet of inductor, capacitor and resistor among the differentials I, V, Φ, and q.

Commercial Unix extinguished themselves without much help from Microsoft. The Halloween documents were about Linux after all (over 20 years ago!).. the commercial Unix players have only themselves to blame. Unless we’re going to blame all the mistakes of DEC, HP and IBM on Microsoft. Like geez.... even if that’s true then frankly Microsoft deserved to win.

In my day, bricked meant recovery was impossible without dragging out a soldering iron. This gave way to needing to at least physically disassemble something to get to a jtag or similar port. If you can recover the device with user accessible buttons and and standard cables... it’s not bricked in my book.

Even an el cheap basic managed switch will do port mirroring

Ttf has bytecode for a stack interpreter with conditionals and loops (jump instructions and loop all). That’s declarative in the sense that all code is data, but i would say it is imperative.

Lol you’ve never stolen a book from the library before either intentionally or not? This should be pretty straightforward but the more valuable something is the more incentive there is to steal it. Meanwhile, while you can throw more money at physical security and scale it up, technology hasn’t changed much in 50 years let alone 20 - you hire enough people at considerable expense and implement good basic security systems. This costs money and stupid tech like “slap an rfid tag on it” doesn’t change anything

The fidelity of standard non high bias tape at compact cassette speeds is already shit compared to even low bitrate mp3. It’s not a problem in practice.

Suffice it to say that Packard was involved in X before XFree86. But the point was that although he was an actual productive contributor he was far from working outside of a consensus. There’s really no sides here. The market could have continued with XFree86, it did not.

I don’t see your point. A large base of Nim users are looking for a pragmatic alternative to the C/C++ family without the aggressive anti-modernism of Go. Nim is certainly not the only player in this realm, but far as I know there isn’t a “Nim Drama” Twitter or tumblr. The drama queen stereotype of Ruby and Rails is very well earned on a repeated basis. All the communities have had their dramas but Ruby and Rust to a lesser extent seem to attract it a lot more as a pattern.

Like many CA laws I don’t see how this is practical. Unless there is some reference to market ranges or something might as well say range starts at minimum and up to whatever made up budgeted amount, depending on experience.

And I suppose Kubrick wasn’t a director either.

I mean I think the “sole” contributor your are referring to is Keith Packard? Don’t see any reason to not name names here. In any case I guess what I find odd is that while he did a shit ton of work in spearheading a fork, it’s not like it was just him. There were a lot of people, greatly outnumbering the XFree86 steering committee that were unhappy with the direction of the project. It’s not like it was just Keith. That’s what I find odd about your assessment. Obviously there was enough consensus to fork.

> I seem to recall reading at the time that the XFree86 core team was unhappy that a sole contributor was attempting to modernize the system by introducing extensions, without building consensus around them to their satisfaction.

This is a kind of odd retelling/interpretation of events, considering the “rogue” contributor version is the only one that lived and XFree86 is history.

For a time in the 90s it was very popular. It was often paired with AOLserver for web applications. And it became a glue/scripting language for some heavyweight programs like EDA tools. I mean it was popular enough to somewhat ironically just pull it into the python standard library.

> Why do you think modern CPUs still expose mostly C-abstract-machine-like interface

I don’t think that, because they don’t. Your premise is hogwash.

Modern RISC derived CPUs for the most part expose a load store architecture driven by historical evolution of that micro arch style and if they are SMP a memory model that only recently has C and C++ adapted to with standards. Intels ISA most assuredly was not influenced by C. SIMD isn’t reminiscent of anything standard C either.

Also you might want to look into VLIW and the history of Itanium for an answer to your other question.

This is not bricking. And really has nothing to do with smart devices. I assume this device could be recovered through the usual wired diagnostic port means, so the reception issue is an annoying situation but not anything close to “bricking”

It’s a little more to it than that... I think you are severely understating the necessity of “speeding up the process.” IP concerns aside, an internal scan chain may still not give you features such as practical monitor mode debugging with any useful level performance. The point is, debugging in general is better served by dedicated hardware, at that point putting it on the jtag bus vs any other serial bus is more a basic pragmatic issue.