If you work for a company that has cybersecurity insurance, they ask, point-blank, if all employee desktops have antivirus before they quote your premium. You just have to use it. It’s not a subject for religious dogma.
Yep MacOS only for now. SSH works ok, it wraps the native SSH and does some magic so your milage will vary. For TMUX, don't know what you would need that for honestly.
>For TMUX, don't know what you would need that for honestly.
It's super useful for doing things on remote servers. Tmux can maintain a "session" between ssh connections. So I can start a long running process on a tmux pane and then log out and come back to it later to see how things went. I also generally do development over SSH so it's nice to not have to re-set things up each time I SSH into the VM.
In the US the America On-Line (AOL) internet service provider mass mailed 3.5 floppy disks to households. This was a boon for all my classmates when I attended a vocational school that required us to submit assignments on disk.
I would remind everyone at family gatherings that I was collecting them if they didn’t need them and quickly had about 15 I could use.
Making some assumptions about what you mean by "business logic application backend." Taking it to mean the business logic layer in an application stack that sits between the presentation layer and the data access layer.
This style of application development benefits from an object-oriented language. Where an object encapsulates the domain logic of business rules. This can be accomplished in Go with structs and funcs.
Classes in Java make good domain models because of (overbearing) enforcement of file structure (object creation validation rules in the constructor, limit access to properties to getter/setter methods that can verify inputs before mutation, yadda yadda). In domain models, neatness and organization counts a lot for the long-term health of the code.
My opinion is that Go is well suited to the task of creating autonomous worker applications that enforce business logic rules for domain objects with well-defined borders. If your domain objects have overlapping concerns or you have actors/business rules that need access to more than one domain object for calculation/mutation you would be wise to think carefully about the application structure before selecting Go as your language.
I’m not happy that this change has happened; however, since learning about how the BOOTSEL mode works under the hood I’ve been expecting news like this from one of the big two OS vendors.
While a sleek looking use case on the surface, mounting the PI as a fake, non-standards compliant, mass storage device is just a hack.
I'm not sure which part of the standard you think they're violating but the Pi is presenting itself as a USB device. One that accepts a (limited) number of blocks of data, and can respond with blocks of data.
Drag and drop to program isn't the same thing as flashing an EPROM on a chip burner like we're still back in the 80's, but that's because time's moved on since then.
> I'm not sure which part of the standard you think they're violating
The part where you're not supposed return a successful Command Status claiming a write succeeded, when actually, you're dropping writes — to anything but a few specific blocks, and only if you see those writes in the order you expect — on the floor.
Oh whew, that's just some layer 7 concerns. I'd be interested in seeing where that's (that it must actually write those blocks) actually defined by in the spec and what language they use. I was worried my Pico was sending invalid blocks that didn't properly parse and was relying on undefined behavior to implement flashing.
It may be a hack but it isn’t a new idea. MBed DAPlink has had drag and drop programming for a long time. The STlink programmer also does this, so do the Segger J-links.
