noobiemcfoob

Anecdata vs. Anecdata: My high school calculus course (AP Calc BC, so college Calc I and II) was phenomenal. It let me jump into Calc III at college and get an A+.

Ideas that there is a huge difference in high school vs. college math is more that there is a huge difference in math teachers and course expectations.

JavaScript is the perfect example of give hackers a bit and they'll take a damned terabyte.

I believe fbs might have massaged some of your GUI packaging problems. I haven't used it myself, but a coworker who builds a Windows GUI application swears by it. From him, "It's the package manager python doesn't deserve"

https://build-system.fman.io/

Ok, but most doorknobs aren't brass.

You mean...like the doorknobs?

"Evaluate it in a try..catch or whatever your language provides."

"That's not very enterprisey of you"

Oooh, I'm laughing so hard it hurts. It's been a particularly 'enterprisey' week at work.

It's not just "not bad." It's scary. It makes enough coherent sense from sentence to sentence that I doubt my mom (missing a few marbles) would notice it doesn't make a whole lot of sense. Combine this...some official looking logos and a request for money for a fine.

Determining an actual official government or other institutional request is going to get much harder.

It's a similar issue in presidential debates. Someone needs to have the authority that something is off topic or off the rails or whatever, but they have to balance that against things that need to be said. And the choice has political implications, big or small politics.

The whole point of structure in these types of dialogues is to reveal the nuggets worth talking about, not cover them up in favor of following the rules.

I just used this on a random project I happen to be building documentation for. I'm pretty in love with the minimalism of 'portray'. I wish there was a chance to get my team to use it, but I'll definitely be using it in my personal projects going forward!

Ah, noted. Thanks for the education.

Gladness you don't have it is criticism you're trying to hide behind semantics.

You and I seem to have different ideas of an employment social contract (or non-existence of one). Unless you're interested to dig into that difference, I don't think we have anywhere else to go with this thread.

> In my country, which (thankfully) lacks America's "at-will" employment contract

I'm sorry, is that not obviously criticism? My parser must be busted again.

> it does mean that it's quite hard to fire an underperforming dev, because how the hell do you prove they're underperforming? What metric do you use?

I think your criticism of 'at-will' employment is unfounded in this scenario. Having lower guardrails on employment means it's not as pressing to figure out performance metrics. If the company narrative is that an employee is helpful to the mission, then there isn't much cause to fret for a more perfect metric. And at-will means you can test more employees before committing to a few for longer than a couple years.

How curious that one of the best models of intelligence is one of its products created in an effort to emulate itself.

Are most people in the type of shape that 30 seconds per mile variance day to day is surprising? I don't time myself, but I'd be surprised if any two of my sprints aren't this different normally.

I don't think it's more. I'd happily argue 80% of people keep to themselves 80% of the time, but those 20% gaps are highly visible in contrast.

But to the point: What's the socialite's internal monologue while being all chatty? What's the overlap between what they think is happening (e.g. what the script is, what the norms are) and what third parties would see?

I see social people who obviously feel connected to the group, but how much of that is just eating up their own internal version of what they see happening while ignoring the smell of any mentally suppressed interactions?

That's my secret, Cap. I'm always faking it.

/Just like everyone else.

Seriously, some of the less intrusive locations on the spectrum just strike me as being particularly vocal about logical inconsistencies to one's own detriment.

Piloting helicopters is complicated. One of the features touted here is simplicity to learn. It's also a lot smaller than most helicopters.

But otherwise, yeah, that's a current use case of helicopters.

Fuel efficiency, noise, flight time, max and min speed and load. Depending on these and some more I can imagine plenty of scenarios. Park rangers and other areas that have difficult to access portions come to mind.

If you won't follow our rules, I'll make another rule that says you have to!

Can a court coerce a murder witness to testimony with imprisonment?

Sure. Expand my question then to imprisoning someone to coerce testimony.

> Imprisoning people who have committed crimes

That's not what is being called into question. It's imprisoning someone for the express purpose of coercing testimony that smells here.

I can accept your argument, even if it leaves me grumpier than when I first asked the question.

States convention, anyone?

I like the concept, but the separation of church and state is only nominal in the first place. Barriers that obstruct one aspect of culture from influencing other aspects are good, but these aspects are ultimately part of the same whole.

How is admittedly imprisoning someone for "coercive" reasons not cruel?

/I'll table the unusual bit.

Yeah, I did miss the import from protocol.py. I knew it couldn't be just 60 lines but got excited and hit enter. Regardless, to your earlier point, I don't dig into the protocol's details often and just rely on the library.

Micropython and this WebSocket client DO run on the ESP8266. As noted before, I'm using these libraries on a D1 mini. I don't know the specifics of the memory footprint as I stay away from applications where I'm up against the wall of my device's capabilities. But the point stands that there's plenty enough space on the ESP8266 for the glorious luxury of micropython.

> What is used in embedded makes sense for embedded only

Certainly, with that attitude. Personally, I fight that mentality when I can. The reason to lean on technology that is used in multiple disciplines is to increase the pool of viable programmers. If it's the wrong tool, then it's the wrong tool. But otherwise use the tool that the most can use.

On porting libraries...well, the WebSockets client I play with is only 60 lines. So, I don't know, you tell me: https://github.com/danni/uwebsockets/blob/esp8266/uwebsocket...

And yeah, that's micropython (because I love inviting the wrath of embedded developers). But that will run on your ESP8266 just fine. I use the D1 mini :)

You're definitely right on having to implement more of the pub/sub on your WebSockets server. I misspoke in saying WebSockets gives you those qualities.

This is a much better argument than your first comment.

For a persistent connection, you might want to move from HTTP to WebSockets, which also brings the bidirectional quality and some more of the pub/sub qualities. Though WebSockets' complexity compared to just HTTP is similar to MQTT.

Being able to implement the protocol yourself is less something I would do in production and more a comment on how easy a protocol might be to grok.

I wouldn't expect to implement my own WebSockets client. So this and the relative overlap of features puts MQTT and WebSockets in the same bucket for me (far more so than MQTT and a raw socket).

Summarizing my views: MQTT seems as opaque as WebSockets without the benefits of being built on a very common protocol (HTTP) and being used in industries beyond just IoT. The main benefits proponents of MQTT argue for (low bandwidth, small libraries) don't seem particularly true in comparison to HTTP and WebSockets.

Both MQTT and HTTP are built on top of TCP sockets.

A HTTP client can be implemented by hand with just a few examples in a few hours. I was unable to do the same with MQTT.