I definitely comprehend coding language better/faster when I want to fully understand a program. I usually skip docs and go to the sources when possible. I think it's deeper than just the code though, the biggest thing I haven't seen in using natural language is good organization to express the program.
100% agree. It's crazy so many Ai articles are heralding the end of code while at the same time defining more complex ways to write code under a different name.
I have a hard time imagining anything where writing a browser wouldn't be an excellent transferable foundation. Even your example: writing css will never teach you as much as writing a css engine.
I feel like your example exactly describes why the development pipeline is production. Just because the critical hours of the system are different doesn't mean it's any less important.
This exactly matches my experience. I also suspected that it was my higher threshold for code quality but Ai generated code is just not worth adding to a project without very strict reviews, unless it's non production and I want to fully give the project over to Ai
But those are the parts where it's important to struggle through the learning process even if you're slower than AI. if you defer to an LLM because it can do your work in a new codebase faster than you, that code base will stay new to you for forever. You'll never be able to review the AI code effectively.
When I first heard about these I thought eink had gotten cheap and good enough for that to be part of the display. The fact that it's just a regular tv displaying a painting was so disappointing.
I assume the nuclear reactors are to power the data centers using the new chips. There have been a few mentions on HN about the US being very behind in building enough power plants to run LLM workloads
That's if the website you're querying is a static html file but the web is much more dynamic and varied. Some of the questions I have: does yesnotice execute js, does it handle an answer appearing on a different page, does it handle ambiguous launch language. In essence: how does it work?
The comments here are pretty surprising. a lot of commenters are very worried about something that seems like a very reasonable change. The license change is to prevent someone like AWS offering managed-liquibase. It might not be technically open source anymore but why does that matter? You can still read/fork/contribute to the source and leverage liquibase internally. The fact that liquibase the company exists and provides this library is great. They shouldn't have to live in fear of their hard work being co-opted into managed liquibase to pass some open source purity test.
For people who don't or can't have Ethernet wiring, I've had great success with Ethernet over coax. My ancient coax wiring gets 800mbps back to my router with a screenbeam MoCA 2.5
I'm using it for a browser extension, just because I wanted to code more in rust. It's great at what it does and has all the same paradigms from React. The best use case though, would be if all your code is already rust. If you have a complex UI I'd probably use react and typescript.
This is a great write up! For people using gradle to compile scala (definitely not my first choice) the initial hurdle to migrating individual modules has been fixed! I'm guessing it'll be in gradle 8.13 https://github.com/gradle/gradle/pull/31118
People have already mentioned Metal, but if you want cross platform, https://github.com/gfx-rs/wgpu has a vulkan-like API and cross compiles to all the various GPU frameworks. I believe it uses https://github.com/KhronosGroup/MoltenVK to run on Macs. You can also see the metal shader transpilation results for debugging.