https://www.reddit.com/r/webdev/comments/hbx5oy/why_do_we_not_see_more_3d_websites/ https://www.quora.com/With-WebGL-and-three-is-3d-on-web-is-now-easier-How-long-would-it-take-for-people-to-adopt-3d-websites https://www.reddit.com/r/gamedev/comments/5d5k9q/why_hasnt_browserbased_3d_become_wildly_popular/ https://www.reddit.com/r/web_design/comments/hbwvqt/why_are_3d_websites_so_uncommon/

https://news.ycombinator.com/item?id=38477211> We’re still waiting for our “react” moment on the backend; a fundamental shift in the abstractions we treat as the bedrock of our applications. https://news.ycombinator.com/item?id=37597705>

https://github.com/gosub-io/gosub-engine https://github.com/runvnc/tersenet https://www.palemoon.org/ https://webllm.mlc.ai/

buck2 https://github.com/facebook/buck2> https://hub.docker.com/r/chainguard/buck2> https://www.google.com/search?client=firefox-b-e&q=hacker+news+buck2+> https://news.ycombinator.com/item?id=35470371> buck2 is arguably the state of the art currently, it is developed by meta based on the learnings from their own buck tool and bazel(/blaze), and others: https://news.ycombinator.com/item?id=41122736> Buck2 is IMO much better than even Bazel is from a design POV, because it actually cleanly separates all user rules from the build engine, and has a coherent modern design around a sound theoretical basis. Neil, one of the leads and author of this post, has written many build systems, so it’s not like he’s unaware of Bazel; his taxonomy of build systems and ones like Bazel in “Build Systems a la Carte” is worth reading even for Bazel users.

https://github.com/maidsafe/safe_network https://maidsafe.net/ this one quite interesting devs Bartozzz/offchan.org: WIP: Offchan is a modern, real-time, anonymous cyberpunk image board. The main themes are programming, technology, science, psychology and philosophy. (github.com) mrusme/superhighway84: USENET-inspired, uncensorable, decentralized internet discussion system running on IPFS & OrbitDB (github.com) https://github.com/satellity/satellity elkarte/Elkarte: ElkArte Forum. A free, open source, modern discussion forum / BB (github.com) this has some small activity https://github.com/Southclaws/storyden this one small activity, but something keeps happening there very cool aesthetics everyone can change the data F4IF/ctree-demo: Collaboration Tree - A community discussion platform built for maximum insight with minimum oversight.

https://news.ycombinator.com/item?id=39026661 https://www.reddit.com/r/golang/comments/9pg20f/go_is_from_a_theoretical_perspective_a_very_bad/ https://xetera.dev/article/thoughts-on-go https://news.ycombinator.com/item?id=34188528 https://blog.carlana.net/post/2023/ten-years-of-go-good-bad-meh/ https://nathanleclaire.com/blog/2014/04/27/a-surprising-feature-of-golang-that-colored-me-impressed/ https://github.com/earthboundkid/flowmatic

10x engineers from 20 years of experience actually? https://news.ycombinator.com/item?id=39358149

opinionated quotes - into my own blog https://github.com/dwmkerr/hacker-laws this one not that great https://github.com/castorm/engineering-principles 1.25 ^ 10 ≈ 10 https://news.ycombinator.com/item?id=39413832 let small fires burn https://swizec.com/blog/let-small-fires-burn/ By centralizing services and standardizing your tooling, Backstage streamlines your development environment from end to end. Instead of restricting autonomy, standardization frees your engineers from infrastructure complexity. So you can return to building and scaling, quickly and safely. https://backstage.io/ release form https://www.aprilsoetarman.com/Unfinished-Projects-Release-Form kwargs large hammer

overengineering https://www.reddit.com/r/ExperiencedDevs/comments/rwtf29/how_do_you_avoid_overengineering/ You start a new project with a code base you know you are going to throw out. You make it neither pretty nor optimized. You do the bare bones minimum to get the main feature you need to work in some small way. I got told by a boss recently that if you are having fun creating the solutions it’s most likely over engineered. Simple code should be boring lol

The problem with the SMARTEST software engineers is they are incapable of distinguishing between good and bad code. They’re fantastic at writing EFFICIENT code, certainly, but not code that is comprehensible by others - all code is equally comprehensible. https://news.ycombinator.com/item?id=18207184 python bad https://news.ycombinator.com/item?id=34177703 atoav on Dec 29, 2022 | parent | prev | next [–] I, a python dev with a decade of experience sometimes still need half a day to figure out some weird dependency venv import-path issue.