qppo

"Orthogonal" in this context means "wholly and completely unrelated." It's not a buzzword.

I think you have a false dichotomy.

Slack and email are for talking to people who I'm not on the phone/video conference with or are away from their desk when I'm working. That is an orthogonal problem from the "Maker" tools you listed.

Jira is for specifying future tasks and goals, it's also an orthogonal problem to the tools you listed.

Fat chance of this changing anything. Berkeley is liberalism run amok. Unless you already own property in one of the shrinking "nice" parts it's not that nice of a place to live, and loosely committing to allowing multifamily zoning is not going to change that.

I'll bet money that even if the commitment turns into law in 2022, it will still cost north of $1,000,000 to actually construct or convert a multifamily property due to ridiculous permitting costs that you can't see up front.

To me, there's an irony that the nationalist desire to sever Britain from the EU is the best way to hasten the dissolution of Great Britain. Now that Brexit is done with, reunification of Ireland and Scottish Independence are in the conversation.

I'm also not British so I don't know how serious those conversations are. But the assured economic and political disaster of Brexit wasn't enough to stop that ridiculous idea, so who's to say the same won't happen to the marginally less ridiculous proposition to reunify Ireland and establish an independent Scotland for the first time in centuries?

Compilers seem to manage just fine with bootstrapping themselves. The trick is not to overwrite yourself

Why do you think they had an incentive to prevent it? The President was the one encouraging the insurrection!

I haven't seen these calls for surveillance. I have seen calls for sedition charges against the politicians that encouraged it and law enforcement that ignored the evidence of coming insurrection.

Interesting how the decline of child labor in Korea is followed by a booming high tech economy while regions that remain affixed to the practice havent

It's hard to lift the next generation out of poverty when children are working instead of going to school.

VSCode extensions are driven through "commands" that are exposed through the package.json of the plugin (which can be parsed by other plugins if you wanted) and issuable through another plugin, or using a task (this is kind of annoying though and not a first class use of tasks).

I'd question why you're running code in a meeting. That's some morning standup stuff for your team which can be done at your desk or placed in a gif in an email, not hauled off to a separate room.

Meetings are for collaboration, not demos...

All my presentation materials are in the cloud somewhere, I don't need to bring a computer anywhere these days.

You can do all that and more in vscode as well... you just have to "learn to master and config" it with your own plugins in JS. It's not that hard.

I don't know how this should be structured but there has to be some principle of "use it or lose it" for IP protections, and some limitations on transference of IP.

Obviously there are a lot of negatives to implementing some kind of legal framework around those ideas but something has got to give here, the existence of patent trolls and defensive patent strategies is offensive to the notion that we should encourage innovation.

I think the answer is to look at things that can't be done by executing code from a library. In other words, think about something you can compile that isn't executable code.

Some examples: hardware description languages (VHDL, Chisel), human readable graphics languages (shaders, SVG), languages for describing music or instruments (super collider, SOUL, Max/MSP, Pure Data), other creative coding, generative art, etc. Essentially think about all the things that programs arent, and think of how a DSL can represent them - be it abstract information like art, physical things, or other things not readily represent able as digital data.

But to the first part of your question: it's not hard to make a DSL. It's hard to make one that people will use. The hardest problem in developing one is dogfooding it, you need users from Day 1 to give feedback on what works and what doesn't make sense. Another way to think of it is that the technical problems of DSL development are straightforward, the social problem of making one that's useful isn't.