noobiemcfoob

Can someone justify MQTT over HTTP and WebSockets?

Before you jump down my throat, I've used all three protocols to a fair degree. MQTT was the most painful, and without strong justification, what's the point? I always read a bandwidth usage justification, but if that's the case, someone should be able to tell me the number of overhead bytes saved using MQTT over WebSockets.

It wasn't so much a promise however long ago as much as a lot of MBA-style thought had yet to be put into the monetization strategy. The games that were made tended to be made for artistic and entertainment motivations over a boardroom identified market niche that is somehow the exact same niche filled by every other game.

Eh, Breath of the Wild notwithstanding, I haven't found a game, indie or AAA, that scratched that old itch in years. There is a glut of games, for sure, with no easy way to filter them and no promise of a game I will actually enjoy.

You miss the point. Those 80% didn't just choose low cost optometrists. They don't need high-end optometrists. A specialist with all the qualifications to help the issues with your eyes is far and above what I need to fix the relatively minor flaws in mine.

Does a ton for you, if you need a ton done*

I have sympathy for more complicated cases, but they're the 20% approaching 0.01%. They necessarily can't be used to justify the 80% case which is as the GP described.

This isn't an event but a teardown of a business model on the basis that the older model users are scared of it.

Everyone knows the manager is the most valuable person in the room. They have the ideas. The rest of us are just implementing their vision. So easy.

/s

One of those seems a lot more powerful than the other...

You still need ventilation systems with electric vehicles. A lot of stuff produces particulates or vapors that need to be vented out.

A free cell phone for everyone should be added to Yang 2020's platform.

And illustrates one of my core problems with Apple stuff: so much is hidden in gestures I'll never naturally discover unless someone tells you. Likely where Snapchat got the idea

Consumer grade 3D printing might be finicky, but I have a hard time saying easily available tech that can create shelves, doorknobs, or pretty much anything smaller than a foot squared "sucks".

For your last question, absolutely. There are $10k+ 3D printers available that are a marvel and have dramatically reduced design time of mechanical components.

"the other platforms" leads me to suspect you haven't tried many other window managers. Linux has too many to name.

You...really seem to be reading into my post. Moral necessity for rewarding different risk strategies?

No, I'm not making any overarching claims to be taken up and enforced by a government or similar entity. And diversity of most sorts has value in a population.

Actually, my biggest take away from all this is that it is even more important to stop framing things as zero-sum competitions and more as collaborations where an individual can find a space fitting of their grit, skills and interests.

Follow this strategy too many times and you're out of new foci. It's particularly concerning if you're more fragile against the early challenges associated with a new endeavor. Many things won't look fruitful until you stick with them long enough to see over the first hill.

We did. Even in a hierarchy, an executive's primary role is to build consensus, but in a co-op you're contending with increased ego from the participants. In a hierarchy, not being the executive makes it easier to back down on an issue. In a co-op, part of your mind must see yourself as an owner. In a co-op, every active employee needs at least some degree of CEO-ness. And then you have too many CEOs in the boardroom.

> that difference doesn't have to be a death sentence

Despite my failed attempt at one, I completely agree. To me, the co-op must be the way forward. It's the only likely contender I've found that might bridge capitalism and socialism.

Except, in identifying the freeloader, being far less invested in the outcome (e.g. further from the problem) is a benefit as it provides some objectivity. Create a co-op group and convince them their survival is dependent on each other...I highly doubt a group beyond 5 will agree on who the freeloader might be.

I tried to start a tech co-op. Ours failed because of a lack of shared definitions on too many topics. What was 'work'. What was 'learning/training'. We could agree on goals, but intermediary steps towards those goals were all over the place.

Without a clear provider of vision and decision, it crumbled. This part is true of any venture, but I think becomes even more critical in a co-op since the authority is necessarily shared.

Congratulations! You're all right!

Maybe, but it's that type thinking that permits the behavior in the first place. People built the workplace and people decide what is acceptable.

Deciding to leave doesn't mean put in your notice. It means look elsewhere. Leaving a job without another secured is always precarious absent a nest egg.

No job is interesting enough that I would tolerate targeting and succeeding in firing a productive employee for internal politics. Doubly so if that behavior is coming from a department nominally in a support role. That's a dog to be put down.

Because of the same misguided sense of hegemony the parent references.

I mean memory, storage in a broad sense. Not a statement about in RAM or cache, though I see the confusion in retrospect. Having code access some sort of storage (better word than memory) is always the most expensive part.

A workflow using the code is a itself a type of test. If something breaks, the users will tell you. A lot of code ends up in that space because it was never asked for as an actual project, but now a team relies on it but no developer can be officially assigned to it.

Memory access of any type is often the slowest. This might just be a general law of computing regardless of level of the stack at this point.

In the serverless world, memory accesses are the most expensive with writes being the most expensive of all (where expensive == slow AND literally expensive)

The serverless database options still remain the bottleneck though. They are still often the slowest aspect of any logic path if not also the most expensive.

This is exactly my perspective. Existing ISAs have a de facto stranglehold on the mindset around computer architecture because they could provide a consistent foundation while the underlying implementation got better and better faster than anyone could build something on top of it.

There have been plenty of small experiments in other architectures but never enough of a mindshare investment to really evaluate viability and performance of alternatives. There are costs to a more diversified architecture eco-system, sure, but I fully believe we will find more value in that space than we have so far taken advantage of.

ASIC implementation of a PLC, anyone?

I, for one, welcome the end of our Moore's Law overlords.

This race to increase various aspects of performance has long let the fields of architecture and the software on top of it be lazy in their optimizations. When there's no more juice in that fruit to squeeze, I know there is much more to be found elsewhere.

/I can't wait for my non-von neumann SoC FPGA hybrid to use for...I'll figure it out then I'm sure.

> sophisticated networks of trust, content raters and algorithms that would tell you what is worth reading

Didn't this happen? Some versions more formalized by others but isn't this what people mean by an individual's bubble? The concern being that these bubbles can be so different as to be incompatible with others.

You don't need laws for that. You just need companies offering it and consumers choosing it. Which won't happen until it's easy to do.

Consumers can change a lightbulb and little else. Make it that simple.