316 karma · joined March 30, 2016
If it's taken someone a whole fortnight to write it, you should expect to spend at least half a day reviewing it, IMO.
Go is well known for having laborious error handling (prompted by a lack of exceptions) and masses of boilerplate and verbosity precipitated by the lack of various other features, the most glaring of which is an absence of generics. This means implementing custom data structures is generally an exercise in copy paste, or ignoring type safety.
Things like the lack of extension methods, JSON and YAML serialisers that require explicit annotations everywhere instead of conventions, the lack of OO/polymorphism, no ternary operators, null chaining operators, etc. etc. also contribute to the verbosity.
Simplicity is good, but the lack of expressivity and the need for such boilerplate is bad. A pretty poor type system makes it worse. Go has many strengths, but I massively prefer C# for the majority of non-trivial situations.
Regarding performance, it depends heavily on what you're doing. For example, Go's allocator and GC is designed to optimise for low pause latency, whereas dotnet is optimised more for high throughput and good cache coherency. Given the extent to which most apps are stalled waiting for memory, the lack of good cache coherence in Go allocations, and the lack of a generational GC can absolutely decimate performance. DotNet is capable of allocating at 25x the speed of Go, for example.
Go read https://medium.com/servicetitan-engineering/go-vs-c-part-3-c...
Augmented Reality contact lenses are the modern equivalent of 1950s predictions of nuclear-powered flying cars.
I don't think smartphones will really be replaced for forty years or more. It sounds like a long time but it really isn't. We've not come that far since the original iPhone. And that itself wasn't that much of a leap from various form factors five to ten years earlier - just a lot slicker in terms of UI. So phones will just get better. One can easily imagine the battery tech improving, perhaps practical rollable or foldable screens, lighter weight, etc. Fundamentally one wants something that easily fits in a pocket (current modern flagship phones are too large), provides a good display for interactive content and allows silent text and voice input.
I think cars, phones, tablets, laptops, desktop computers and TVs will all converge more in terms of control interfaces. There's plenty of evidence of this already with Android Auto in things like the new Polestar 2, the decline of custom TV software in favour of Android/Amazon's FireTV OS, etc. That's felt around the corner for years now, but feels like it might finally happen soon.
Evolution not revolution, in other words.
Perhaps your views are more a reflection on people getting pigeonholed at large companies, or otherwise choosing to specialise? Or something like that?
I personally think it's hard to be a _really_ good frontend dev without a chunk of more general development experience. What wider experience will you draw from to solve hard frontend problems otherwise? If your Angular/React app isn't performant enough because of the computations it needs to do or allocations it needs to make, how big is your mental toolbox to fix that if you haven't done more general backend dev work? It's all just software, ultimately.
Amazon used to be great. Nowadays it's full of fake reviews and dodgy secondhand stuff being sold as new.
Secondly, unless you're selling compiled software for others to configure, there really is no difference between config in config files and config in code, except that the former does not let you build such meaningful and useful abstractions. You're presumably delivering it all into production via CI/CD anyway, so what difference editing a config file vs. some actual source code, besides the lack of real type safety and IDE assistance?
Pulumi have figured this out.
(And I suspect that if your end users need to configure your software's use of Spring's Dependency Injection in XML config then you are probably doing it wrong.)
There are green screen plugins for that. You could chain Snapcamera's virtual cam output into OBS and use OBS 's chromakey filter to underlay whatever other content you like. Y I u can then output OBS to another virtual cam output for use in Zoom or wherever else via the Virtualcam plugin for OBS.
It'd be really nice if someone would make a nice OpenCV virtualcam output so one could drive all this from a (relatively) simple Python script.
This is a frequent gotcha with Typescript, where even if your type is declared with a Date field, Javascript won't care when it deserializes it, as that type information is all erased and not available at runtime.
(Also, Number in JS being floating point and all, it lacks the integer precision for high resolution timestamps - if you start serialising 64 bit timestamps and expect a JS-style runtime to do good things with them it doesn't end well.)
The author seems to have expended great effort on terseness, writing in very short sentences which artificially forced him to start more of them with coordinate conjunctions than feels comfortable to me. It did not make for an easy read and all felt rather too self-conscious. Good writing should focus me on the ideas, not the annoying syntactic structure of the writing.
I didn't get on with it.
I'd be far more worried about the invasion of privacy caused by it listening to everyone's shopping lists.
Let's say you're writing an IDE in it. How would you invoke compilers & debuggers, cache filesystem/type information, state, etc. without breaking out of the browser sandbox somehow?
Your web site shows me diddly squat. Do you actually _have_ a product? Where's the video walkthrough, or at the very least, some screen shots?
If your product were genuinely useful / insightful (which is very hard to do in this space) then we might buy it. For 400 seats. But it looks like vapourware to me right now. Come back when you actually have something to show the community.
Check out https://m.youtube.com/watch?v=48KtJtDqkaM for a 4K Vista Pro animation render!
I'm amazed to discover that Tornado has gone open source and is still being modded by people: http://www.moodurian.com/
https://archive.org/details/Project_Stealth_Fighter_1987_Mic... for another blast from the past.