![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
I would use reportMissingData
I would use reportMissingData
So then he’s innocent, case closed.
I really really like this idea. I hope work on this continues, though it seems to have slowed recently.
I was thinking the same thing, until I read Minecraft. Java mods…
Lapce looks pretty cool, for an alpha.
Try to recognize friend from foe, everyone.
Check for an asterisk after the file name (in the tab/title bar), it means “unsaved changes”.
Wouldn’t this serialization format need to be implemented in every language that that needed interoperation? How does that differ from an ABI?
Check out the ABI concept, if you haven’t found it yet:
https://www.webassembly.guide/webassembly-guide/webassembly/wasm-abis
What do you think about compiling to wasm, for these logical inter-exchanges?
Scroll down…
Being able to document the exact algorithms used to solve a problem is sort of a ‘Holy Grail’ in programming. Most programmers aren’t afforded the time to document to that level. This would require refining the code down to a single cohesive story that describes the functionality of the implementation. It’s great when you can spend the time on it, but the problem is that the code is actually “working” long before that point. Most employers want to stop paying for code after it starts working.
You know that the US isn’t going to attack China first.
Then there’s the Trump factor…
This is what I’ve been looking for, thank you.
I’ve never looked into it very deeply, but it uses a styling spec called EditorConfig. Check it out, https://editorconfig.org/
Thank you!
If you’re using visual studio (2022 is current) the idiomatic styling will be mostly correct by default (Ctrl k,e will reformat).
So, the question is, how do you deliver better code faster?
I think there question needs to be: how do we convince people that it’s “worth it” to pay for better code?
I get it, we all want to do our jobs well and excel in the craft. The problem i see here is that the stated need for cleanup, refactoring and documentation is immediately followed with a ‘but’. But there is no but, imo.
Code that “works” isn’t good enough, and we need a full stop right there and heads around the table nodding up and down in unison. But they’ll take the inferior POC build every time over investing in a “good” solution that incorporates lessons learned. Next they complain that it can’t be modified easily (“but, it’s just a simple change!”), and bemoan the state of software development.
You’re absolutely correct, they’ve been working hard at creating this situation. I think the left will need to get mean for anything to change, maybe this is a step in that direction.
I agree that report and record are different. To me record means it’s preserved in some managed way.
This makes it sound like the intent goes beyond logging, but not so far as recording. That’s how I come to ‘report’ as the correct verb.