jimmoores

It's basically a micro Unix implementation aimed at old and resource constrained systems. I've been following it for a few years. The documentation is terrible, there are hardy any updates, but it does seem to be making slows, steady progress behind the scenes. I think it just needs to reach a critical mass of functionality and we'll see it popping up on raspberry pi picos, 8-bit micros etc. Definitely needs some TLC in the comms department though. Oh, and don/t be fooled by the archived status - it moved to https://codeberg.org/EtchedPixels/FUZIX

Frankly, if you think that, you're not exactly a power user of office suites. Apple apps are a complete joke in the professional world.

The statement that Apple has been supporting businesses for decades is just the most self-serving bunch of crap. You can tell how thin this is by the way they push local ads on Maps as some kind of headline feature. What a joke.

I unexpectedly liked this. I thought the recommendations were actually useful.

Wow, that is one ugly vehicle. It looks like it's been in an accident.

JetBrains does a great job with this by actually rewarding users who report bugs with free licenses and such.

Delusional.

They're still using CVS?

Why are the words 'Computer Vision' not above the fold on the front page? How am I supposed to know that CV stands for Computer Vision rather than Curriculum Vitae?

I've seen a bunch of companies do this. The problem is always that it isn't Excel. This means usually things like XLWings, Excel-DNA, etc. are actually more useful.

There probably _is_ something in the port compressed up against the back - try scraping around inside with a non-conductive pointy thing.

There has been several articles about this man recently. I come away from them wanting to help him financially. I feel if you're going to publish an article about him, and make money from adverts on your website, you have a responsibility to try and help this man. If not it's just exploitation.

The only thing that might make Apple improve their documentation is if there was evidence that people started actually abandoning Apple's platforms.

Currently it seems there is a never ending supply of developers ready to gamble years of their careers on Apples Terms & Conditions, and while these same people usually eventually realize that there's ultimately no money to be made, they are replaced with a new generation seeking an AppStore paved with gold. Until that stops, the docs will stay piss-poor.

While I have often used a Mac for development and enjoyed it, I don't often actually develop anything for macOS or iOS because, well, why would I risk my livelihood on Apple's whim? They regularly destroy developer's lives with no thought or consequence.

Bizarre, pretty misleading pages about electro-magnetic radiation were a huge turn-off.

On the original ARM2 this design made a lot of sense because if you understood how the instruction timing worked, you could essentially perform as well as a specialized blitter. I never understood this at the time, and largely blame that on a popular ARM Assembly Language book I had that said that LDM/STM were just convenience instructions, essentially syntactic sugar. They most certainly were not. With the right alignment and using enough registers you could get 2-3x the throughput of using single word load/stores. I honestly think if that book hadn't gotten it so wrong there would have been a lot more decent games for the Archimedes machines.

Great book: computer architecture a quantitative approach

You're making a mistake many engineers make in thinking that getting a startup off the ground is all about engineering. Frankly, engineering is often the easy part, and I say that as an engineer who co-founded a tech heavy successful venture backed startup. The hardest thing is choosing a compelling product and then selling it to paying customers. If you think business people undervalue techies, don't make the same mistake by under-valuing business people.

These examples actually were more obscure than the usual list.

When a blog about a collaboration tool devolves into a formal state machine definition and blocks of lisp syntax, I have my doubts about the project's ability to communicate with potential users.

Yes, the communications primitives line up with event synchronizations and the select with the external choice operator, but Go doesn't implement the process operators parallel, seq and interleaved. This is what the guy is getting at, without realizing it. The slightly grandiose noise in the writing kind of reminds me of Wolfram actually (ouch).

This is realised in a real language as occam. I've never understood why so few languages have a par construct, it's much more natural than asynchronous launching.

I've had a good experience running Windows 10 on Azure DevLabs VMs accessed via Remote Desktop from Mac and PC. Even with the VMs running in Ireland (I'm in London), they're very snappy and can happily use Visual Studio, Eclipse, etc. Even video and light 3D works well. I wrote up a blog post on it: https://www.mcleodmoores.com/blog

Having the buck stop with you. With nowhere else to turn, you have to step up pretty fast. It forces you to own your decisions and not run to more senior people to help with your problems.

It's a lot more than 10 rashers. It's about 1kg or 2lbs of bacon (around 100 rashers). Completely nuts to eat that much, if nothing else, the amount of salt consumed would be enormous.

Great to have a resource like this. By way of providing some hopefully constructive feedback, the language seems a bit excessively informal: "Safe Rust is For Reals Totally Safe. Unsafe Rust, unsurprisingly, is not For Reals Totally Safe. In fact, Unsafe Rust lets you do some really crazy unsafe things". I get the idea that's it's trying to be friendly and street, but it's a bit out of place in a document like this (I was just waiting for 'shizzle' to pop up). There also looks to be an excessive use of emphasis (italics).

There's real breadth in their data sources and that's the real unique thing here: the technology itself is not the important thing, it's the data and the agreements they've established with the data providers.

Very cool!