I mean by useless is it's so slow you can't make games or even big projects for GUI, only you can do is AI/ML, Data Science, and basic stuff. I think Rust is better because of its speed and language capabilities?

Equivalents because VSCode and its forks are not an equivalent.

TL;DR Jetbrains is getting worse, more like VSCode. I want out to something as powerful but not VSCode like (which is worse).

Jetbrains has been chasing VSCode's popularity to the detriment of its own product.

The modal commit dialog is now opt-in, behind a nearly hidden, advanced parameter and will be removed in the not so distant future. This was part of their effort to make the UI "leaner" and more like VSCode so now Jetbrains IDEs look more like it.

Some keyboard shortcuts have also had to be changed to be more like VSCode.

Jetbrains used to have a good docker integration, but that's either unmaintained or undergoing work to support dev-containers better - something that jetbrains practically had nearly a decade ago, which allowed you to code on another server (remote development).

AI Assistant and Junie (their coding agents which I have to use for work) have consistently been behind the curve and just keep getting worse. They have 2 separate products for agentic development and can't decide which to keep, so they duplicate efforts and fail at both. Now I'm asking my employer to just give me Cursor like the rest of the team, so I don't have to put up with this Jetbrains crap.

Privately, AI it's non-starter anyway, but my guess is that Jetbrains is also focussing more development efforts on that than actually fixing existing bugs.

The basics about types of open-source software licenses, their differences, how to choose a license etc.

I see a lot of programmers that really don't know much about licensing and just default to MIT.
To be fair to them, it's a pretty boring and headache enducing topic, but I tried to distill it here.

Hope it helps.

cross-posted from: https://jlai.lu/post/41713315

If you maintain or use open-source projects on GitHub, you might have noticed that embedded star history charts (api.star-history.com) in README.md files broke recently. That's because Github killed the API they relied on, citing high costs because people used it a lot. Well done microslop (they even broke their own UI because they forgot to update their frontend).

Anyway, I couldn't let this project die and I happen to have snapshots of star count data for a few hundred thousand repositories (most of those who have more than 150 stars).

I have forked the original project, replaced the way it obtained its data, and published it as a fully open-source, free drop-in alternative: star-history.dera.page.

Migration is seamless and users simply have to swap out the domain name in their SVG image link.

I'll keep the data updated, I have crawlers running ensuring my snapshots get better and better. I will also maintain the project and add a new github-based style for charts as I have heard people complain about the xkcd look not matching the rest of their readmes. Contributions are welcome :)

I’ve been building a small multilingual weather report generator using PowerShell and SQL Server Express.

A script fetches global weather data every 4 hours, stores it in SQL Server Express, calculates a discomfort index, and generates static HTML pages in multiple languages.

Live site: https://yahikoyama.github.io/weather2/

Source: https://github.com/yahikoyama/weather2/

Inspired by this Lobsters thread, and some of the great comments within it, I would like to ask if anybody is doing some hobby programming this weekend?

Ungate is a Cursor extension that lets you use your Claude, ChatGPT, or MiniMax subscription in Cursor instead of paying for API tokens. It proxies requests through a Cloudflare tunnel, supports streaming, tool calls, and vision. Open-source, MIT.

You wouldn't just Download An Ecosystem.... would you?

cross-posted from: https://sopuli.xyz/post/49932334

Try these tools out for yourself in your web browser!!!!

https://joshsim.org/

^ the tutorial for this tool is very thoughtfully done for people that aren't super comfortable with code, worth a look at just for that I think.

https://storage.googleapis.com/fire-recovery-web/dev/fireSeverity.html

https://dse-disturbance-toolbox.org/tools/disturbance-severity/

https://dse-disturbance-toolbox.org/tools/

Last year, the Park Service used the research group’s burn severity assessment tool for the first time after the Eureka Fire in Joshua Tree National Park, which burned just over 200 acres.

“We were able to do a quick assessment of fire severity and help the park with some analysis of how much vegetation and which types of vegetation were within the burned area, and which were in the more severe parts of the fire,” Zomer said.

The park also used the tool after the 2025 Black Rock Fire, which started near a campground in the park and burned 72 acres.

“We used DSE’s Disturbance Severity Tool twice last year to assess post-fire conditions following the Eureka and Black Rock fires,” said Nick Graver, the botany and vegetation monitoring program lead at Joshua Tree National Park and a graduate student in UC Riverside’s Department of Evolution, Ecology and Organismal Biology. “Combined with field assessments conducted by park biologists, it provided the foundation for evaluating fire severity and developing recovery plans for both incidents.”

In addition to the burn severity assessment tool, researchers are now developing a platform to model the future outcomes of potential recovery actions. The platform, called Josh, just launched this year and will be available when the next wildfire sweeps through either park. The park also used the tool after the 2025 Black Rock Fire, which started near a campground in the park and burned 72 acres.

“We used DSE’s Disturbance Severity Tool twice last year to assess post-fire conditions following the Eureka and Black Rock fires,” said Nick Graver, the botany and vegetation monitoring program lead at Joshua Tree National Park and a graduate student in UC Riverside’s Department of Evolution, Ecology and Organismal Biology. “Combined with field assessments conducted by park biologists, it provided the foundation for evaluating fire severity and developing recovery plans for both incidents.”

In addition to the burn severity assessment tool, researchers are now developing a platform to model the future outcomes of potential recovery actions. The platform, called Josh, just launched this year and will be available when the next wildfire sweeps through either park.

You don't know Josh... but you should! Josh is pretty cool actually.______**___**

Radicle 1.10.0 is out!🌻
https://radicle.dev/2026/08/05/radicle-1.10.0

Radicle is an open source, peer-to-peer code collaboration stack built on Git. Unlike centralized code hosting platforms, there is no single entity controlling the network. Repositories are replicated across peers in a decentralized manner, and users are in full control of their data and workflow.

Good used to have the lighthouse, which points to failure in the page. We can still have a 100% perfect score and the page be horrible (mine is a good example). Yet, the business pages are broken, links that aren't working, forms that don't submit, API's that can't load. When the page loads, to start with.

All feedback in the post is welcome.

cross-posted from: https://sh.itjust.works/post/64685863

Lots of programming languages have their own package manager, separate from the distribution or OS package manager.

Going loosely from the TIOBE index:

• Python has Pip
• C# has NuGet
• Javascript has npm for Node.js
• Visual Basic also uses NuGet
• R has a repository of packages that can be installed by running install.packages("something") in R
• Rust has Cargo/Crates
• Go has the go get command
• Swift has its own package manager swift package
• Ruby has RubyGems
• Java has Maven and Gradle (not sure if they are full package managers, or build automation tools with dependency resolution)
• PHP has Composer for managing libraries and dependencies
• C and C++ are the only exceptions I can think of, off the top of my head; libraries are managed by, and coupled to, the operating system

If the answer were as simple as “finding defects,” then a fully automated review starts to sound inevitable (and appealing).

But if code review was also how teams shared knowledge, built collective ownership, spread architectural understanding, and taught junior engineers how experienced developers think, then the answer becomes much less obvious.

That’s the mistake I think many organizations are about to make, and the reason we need to rethink what code review is actually for.

Specifically, the video is about developing a game where all the textures and sounds are generated at runtime using Sine waves. I thought it was high-quality and explained complex math concepts well.

D.eSystem 6.1.0 introduces a small setup and you can choose your UI with D.eSystem 6.1.0.

D.eSystem 6.1.0 on github: https://github.com/D-electronics-scratch/all_D.eSystem_versions/releases/tag/v.6.1.0

All current D.eSystem releases on github: https://github.com/D-electronics-scratch/all_D.eSystem_versions/tags