[-] FizzyOrange@programming.dev 38 points 6 months ago

... if you have a super janky patch file workflow.

If you are using Git like normal people do this can't happen.

[-] FizzyOrange@programming.dev 38 points 1 year ago

Yeah... This doesn't sound promising. Refusing to acknowledge the obvious fact that AI and hostile mods have driven away 99% (not an exaggeration!) of their audience. A visual makeover before the change anything. Trying to sell the Q/A database for AI despite the fact that you can download it for free. They even talk up their job advertising product that they inexplicably cancelled a few years ago (btw I found levels.fyi has a pretty good job database if anyone is looking).

If it were me I would:

  1. Use AI to improve question quality - if people post obviously bad questions get AI to improve it via a conversation.
  2. Make it waaaaay harder to close questions. Like, require 10 votes and allow the asker to reopen it for free once.
  3. Make it so questions can't go below 0 points.
  4. Make it impossible to close as duplicate. You should be able to mark questions as possible duplicates (and the asker can say "yes it is") but if they don't it should stay open.
  5. Maybe even make it impossible to close questions at all. What actual purpose does it solve apart from driving people away?

Apart from the AI that's all stuff they should have done 10 years ago.

It's probably too late anyway.

[-] FizzyOrange@programming.dev 41 points 1 year ago

I don't think that's a surprise to anyone that has actually used them for more than a few seconds.

[-] FizzyOrange@programming.dev 36 points 1 year ago

Not the case. There are binary components.

It doesn't matter though because the Clangd & CodeLLDB extensions completely replace it and are actually waaaaaaay better.

With Microsoft's C++ extension it always rinsed the CPU - there were files I had to avoid opening because then it would analyse them and I'd have to kill it. The code intelligence also seemed very "heuristic" and was quite slow.

Clangd fixes all of that. It's fast, doesn't choke on huge files, and if you have compile_commands.json it's actually the first properly fast and robust C++ IDE I've ever used. You know if you've used a Java IDE the code intelligence just works and is fast and reliable. It's like that.

[-] FizzyOrange@programming.dev 35 points 1 year ago

I thought OEMs only paid like $10 for Windows?

[-] FizzyOrange@programming.dev 36 points 2 years ago* (last edited 2 years ago)

TL;DR: Intellisense works best if you write bottom-up (true) and it means you have to remember less stuff (also true), therefore it makes you write worse code (very doubtful).

So I don’t think IntelliSense is helping us become better programmers. The real objective is for us to become faster programmers, which also means that it’s cheapening our labor.

This doesn't make any sense though.

  1. People don't have unlimited time. Writing high quality code takes time and wasting it remembering or typing stuff that Intellisense can take care of means I have less time for refactoring etc. Also one of the really useful things about Intellisense is that it enables better refactoring tools!

  2. It doesn't make you dumber to use tool assistance. It just means you get less practice in doing the thing that the tool helps you with. Does that matter? Of course not! Does it matter that I can't remember how to do long division because I always use a calculator? Absolutely not. Similarly it doesn't matter that I can't remember off the top of my head which languages use starts_with, HasPrefix, startswith, etc. doesn't matter at all if Intellisense can easily tell me.

  3. You don't have to use the Intellisense suggestions. Just press escape. It's very easy.

  4. It's very well known that making something easier to do increases demand for it.

[-] FizzyOrange@programming.dev 35 points 2 years ago

He's right that it's probably harder for AI to understand. But wrong in every other way possible. Human understanding should trump AI, at least while they're as unreliable as they currently are.

Maybe one day AI will know how to not bullshit, and everyone will use it, and then we'll start writing documentation specifically for AI. But that's a long way off.

[-] FizzyOrange@programming.dev 41 points 2 years ago

They're being diplomatic. From Wikipedia:

The name "Godot" was chosen due to its relation to Samuel Beckett's play Waiting for Godot, as it represents the never-ending wish of adding new features in the engine, which would get it closer to an exhaustive product, but never will.

[-] FizzyOrange@programming.dev 43 points 2 years ago* (last edited 2 years ago)

Yeah except it's named after the play so it's definitely pronounced God-oh. I think people just mispronounce it Go-dot if they haven't heard of the play. Looking at you Mr Linus Tips.

[-] FizzyOrange@programming.dev 38 points 2 years ago

I would say because a) there are zero alternatives, and b) it's pretty powerful; you can generally do pretty much any layout even if it requires hacks, c) switching to something else is clearly infeasible so it's not worth even asking for.

Just have to live with it (on the web at least).

[-] FizzyOrange@programming.dev 39 points 2 years ago

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

[-] FizzyOrange@programming.dev 41 points 2 years ago

Honestly those things just don't sound like common enough actions to be worth shaving 0.5 seconds off. How often do you know exactly how many lines to move a line by? And how often do you even need to move a line that far?

I still don't buy it.

view more: ‹ prev next ›

FizzyOrange

0 post score
0 comment score
joined 2 years ago