4 ms·
I feel it's the other way round.. Everyone is advocating Javascript, python etc. JS webapps are more and more developed directly in the browser in the dev conso
by mto 9y ago
I feel it's the other way round.. Everyone is advocating Javascript, python etc. JS webapps are more and more developed directly in the browser in the dev console, CSS interactively modified to directly see the results.
But this also lead us to code coverage abominations where people write hundreds of tests for manually checking input types that otherwise might crash the thing after two days running because that hashtag less of lists of objects contained a string instead of a float.
Is that fun?
In gaming Unity3d embraces this interactivity by modifying more or less everything directly while the game is running. The unreal engine blueprints show data flows live etc.
In technical sciences there was always Matlab with its interactive mode of development. We have similar technology in data science with ipython, Spyder, jupyter notebooks etc.
Actually I'm seeing more interactivity than good type systems out there. Elm, Haskell & co is something you find advocated in internet forums but rarely in companies.
(and as the author mentioned - those two actually don't have to be exclusive)
- dasmoth 9y agoYes, I don't think type systems (or, in general, "computer science-y stuff") are the enemy here. I do at least wonder about some of the stuff that passes for "best practices" nowadays: CI tools sound like a good idea on the surface, but can serve to (partially) hide complex build and deployment processes where once someone might have just typed make. Automated tests of awkward corner cases can be pretty valuable, but easily lead to test suites that take minutes (or worse...) to run on every build. I don't really know how best to get the good without the bad, but giving at least some weight to the "sense of fun" stuff sounds like a pretty good starting point.