Yeah sure, but that’s true of every job. Would you rather be a waiter or a cashier or a cleaner or a teacher or a nurse or…?

The level of entitlement here is insane.

It’s not a browser issue. There’s some weird “responsive” thing that entirely hides the graphs. You probably just have a bigger screen.

Nice! Though a lot of the pages don’t show any charts at all on mobile. E.g. the Pie Charts page doesn’t seem to contain any pie charts? And the line charts page only shows a line chart in landscape which is weird.

Ohhhhh you can’t comment on a specific line of a commit message. I see. I mean… yeah I guess not. That seems like a super niche feature though. How long are your commit messages? I’ve never even tried to do that. Commit messages are short enough you can pretty much just write a normal message not tied to a specific line.

There are waaaaay bigger issues with Gitlab. Here’s one I ran into recently, you can’t search for pipelines. It’s got a search box and everything but you literally can’t search; only filter. So stupid.

I actually just went to take a look at Gitlab issues I have commented on to see what my worst ones are. Guess what… you can’t even search for issues you have commented on!!!

Still, overall it’s the best self-hostable option out there at the moment IMO. I guess Forgejo (truly abysmal name) may overtake it at some point.

In my experience the other alternatives tend to lack solid CI integration. I have yet to find an open source alternative as good as Gitlab’s.

You can leave comments on a commit message. What do you mean exactly?

They do have a ton of tests actually. In their defence, if this task is doing Git things then just killing it when it goes badly is probably the best you can do. Git itself is quite buggy if you stray from the most basic setup. I’ve had it almost completely destroy my .git directory in the past when using submodules.

On the other hand, Gitlab itself is an enormous entirely untyped Ruby monster, with extremely difficult to follow code. Not in terms of individual functions - except for the lack of types mean you can’t really know what they do, they are quite clear and well written. The issue is the control flow between parts of the system. It’s difficult to know what calls what, so I’m not surprised they occasionally have to give up.

I had a play with Deno’s Fresh web framework recently (Typescript/TSX but mainly server rendered). IMO it’s light years ahead of other solutions.

You get full amazing Typescript typing, including in templates (unlike Go for example), but unlike React you don’t have to deal with JavaScript tooling or complex client side state management. It’s a real breath of fresh air. (Ha that wasn’t even intentional.)

I think it will take much longer than that. There is so much legacy C++ code. Maybe 10-15 years.

They aren’t violating it, because they can do whatever they want with the data you give them, including not releasing it at all. What they’re doing is providing it with a completely inconsistent license which says you can use it for commercial use but you promise not to use it for commercial use.

Worse than Sourceforge? Savannah?

I don’t think there’s an exact definition but broadly I would say if it has the majority of these features it’s definitely an IDE:

• Integrated debugger
• Intellisense
• Build/debug shortcuts that start the build in the IDE
• Parsing of error/warnings from the build output into a structured list that you can click on

If you make something with all those then it’s definitely an IDE. Without some of them it’s more debatable. For example the old Arduino editor… I would still say is a very basic IDE even though it doesn’t have a proper debugger - it has other heavily integrated development tools, e.g. the UART viewer.

They’re just saying that so that they have a justification for making two IDEs.

It’s a modular IDE.

I don’t think VSCode’s mantra is that it “just works”. It’s definitely a “platform” IDE like Eclipse was.

It can optionally use a lock file. Not sure about peer dependencies tbh.

there are tools in python to help

I haven’t actually used pex but it doesn’t look like it solves this - it’s more of a way of distributing full programs. The .pex files aren’t editable, which is something you need for this use case.

I imagine this strategy has its share of tradeoffs and gremlins.

As far as I know there are no downsides. It’s basically win-win.

It has them, but you can’t use them from a single-file script. You have to set up a pyptoject.toml, create a venv and then pip install . in it. Quite a lot of faff. It also makes some things like linting in CI way harder than they should be because the linters have to do all that too.

With Deno a single .ts file can import third party dependencies (you can use any URL) and Deno itself will take care of downloading them and making them available to the script.

Some other languages have this feature to certain degrees. E.g. I think F# can do it, and people are working on it for Rust, but Deno is at the forefront.

There’s two things:

Deno: this is a replacement for Node and NPM and prettier and some other tools. So one aspect is that it’s a more modern Node, using standard web APIs instead of Node specific stuff. And the other aspect is it is more streamlined modern tooling - no node_modules, no complicated build steps, built in Typescript support, etc. In fact you can use a single file as a script, similar to Python… but unlike Python you can use third party dependencies, which makes it fantastic for stuff like CI scripts, etc. where you might have suffered with Bash or Python before.

Fresh: this is just a web framework targeting Deno. Honestly I haven’t used it much but I really like what I’ve seen so far. I always found React to be confusing and overkill for most sites, which should really be rendered server side, but also I really like the way you can compose components with JSX/TSX in a real language with full type checking. Fresh gives you both!

I just looked up Deno and it’s part of an NPM stack.

It’s not. It supports NPM modules for backwards compatibility, but the whole point is that it doesn’t inherit the NPM tooling mess. You can go from a new Linux install to a running Fresh project in 3 commands.

Yeah I think that’s mostly a myth. When I looked up salaries they were definitely good (for programming; amazing for the average person), but not “I would write COBOL for that” good.

There aren’t really that many old COBOL systems around. I think it’s mostly just over-reported because you can write an article about how some government department still uses COBOL but you can’t write about one that switched to Java.