4 ms·
>training and best practices <...> the problem of over-under-engineering That’s what you have to have once you throw a bunch of tools, planks and screws at fir
by wruza 9y ago
>training and best practices <...> the problem of over-under-engineering
That’s what you have to have once you throw a bunch of tools, planks and screws at first graders and let them go. In my 20s I used few local enterprise solutions to help local micro-businesses do their accounting. The base system was obviously dumb and too restrictive to create “apps (tm)”, but it did its job very well. One specific thing about it was that it was infinitely hard (read: know C++/COM and be able to investigate platform issues) to create extensions for it and/or manipulate basic blocks like you can do with web trinity. The result is that no one went that long route of dominating the market with shady solutions that have value from non-tech faces, but are technically crap.
Seeing what some devs could do even in these conditions, I can tell that it was a good state of things for the tasks that platform meant to solve.
I may seem jump on topics on this one, but to not write a poem, look: Perl’s tmtowtdi is highly criticized, but what web allows is a “there are infinite ways to do it” paradigm with no basic blocks or “best practices” like you name it.
Summed up: if you’re writing apps that do edit objects, there is no room for custom element offsets, scroll handlers, sql statements (except select for few cases) and knowledge of http cookies, headers, urls, etc. If you can’t define a datascheme with two clicks, draw a form layout by hand and write final logic after 5 minutes, deploying in half a hour, without caring what platforms/databases/browsers/ languages/frameworks/backups/ maintenance/ides do you choose, then there is no room for business or app logic in your head.
>the latest HTML, CSS, and plain Javascript
Today it is like chasing specifics of plain 80386 assembly — the knowledge that ages faster than you can read on it from zero to top professional experience. If things didn’t get better in a decade, then it is a dead end. Plank, screw and hammer problem never gets old.
- tboyd47 9y ago> I can tell that it was a good state of things How can we make the situation for web development more like the accounting platform you described?
- wruza 9y agoWe need more distinct platforms that have specific area experience and engineering behind these. "Web" is driven by advertisement specialists and vendors, what else to say.
- tboyd47 9y agoSo a platform for each category of clients? How would you control who uses what platform?
- wruza 9y agoI think yes, a couple for business, a couple for games, and so on. One for landings and news, i.e. web. Hint: not a platform itself is important, but sort of regular professional committee behind it. E.g. there is no committee now for even basic UI. Ubuntu has it, Mac/iOS has, even Windows has native look and feel to lesser but noticable extent. Web simply doesn’t. Open Windows SDK for example and feel how many areas are not yet covered and never will with current approach. https://msdn.microsoft.com/en-us/library/windows/desktop/ff818516(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/windows/desktop/ff8... Chances are I didn’t understand your second question, but if taken literally: I can’t see how usage control may help. Anyone can use anything at their legal will.
- tboyd47 9y agoThat's not a bad idea, although I don't think you could stop cross-pollination of platforms leading to redundancy and bloat. Perhaps if there was a single (large, but well-organized) team responsible for all platforms, that could correctly identify which features were needed where.
- mattgreenrocks 9y agoExcellent comment. The way we program for the web is ridiculous currently: the abstraction level is way too low. > Today it is like chasing specifics of plain 80386 assembly I suspect the fetishization of the unholy Web trinity (HTML/CSS/JS) is impacting the ability of devs to imagine a better workflow. Case in point: Electron. Rather than take some of the lessons learned from the web stack, such as immediate mode UI being a decent default, they just crammed _all_ of it into a Chromium shell and declared it The New Way To Write Desktop Apps. If the web is your first platform you've spent a lot of time on, then what I'm writing will probably just sound grumpy. And part of it is! But, on the other hand, when something new comes along, it may render all of your intimate JS knowledge useless because it isn't JS, and you need to be able to let that knowledge go. Even if the web as a platform sticks around, history shows that whatever comes next might be less powerful than using raw HTML/CSS/JS, but it doesn't really matter for getting most things done.
- 0xdeadbeefbabe 9y ago> whatever comes next might be less powerful So webassembly doesn't come next?
- mattgreenrocks 9y agoWhatever comes next may not afford all the little nitty-gritty things you can do via HTML/CSS/JS. Imagine a VB for the web that hides that stuff in a better conceptual model: you lose the ability to do some things (potentially) but get the ability to do other things more easily.