News for hackers. Stuff that matters.

ReleaseCandidat

Re:What OS should I drive? on Friday October 04, 2024 @02:57AM (#41738560)
> with vms for the rest.

It's called OpenVMS since quite some decades now.

Re:The Heart of Unix (2018) on Friday October 04, 2024 @12:28AM (#41737828)
Yes, as in "check the number of parsed fields for each line" and don't forget about empty fields. Throw an error and stop the program if the number of columns isn't consistent. Which doesn't mean that you can't parse the whole file and output all errors at once (which is the preferred way, we don't live in the 90s any more ;), just don't process the wrong result. And with usable error messages, not just "invalid line N".
Re:Visual Studio Code is designed to fracture on Monday September 30, 2024 @06:59AM (#41695734)
> For me an IDE "knows" about other files I have open and their relationship with the one I'm editing (usually a "project") and it _i_ntegrates external tools/programs.

With that definition any usable editor and vim-likes ;) is an IDE. I can live with that (that Zed is an editor comparable to them) too.

Re:Visual Studio Code is designed to fracture on Monday September 30, 2024 @05:54AM (#41695346)
It's not an extension.

   First-class modal editing via Vim bindings, including features like text objects and marks.
See the "Vim-friendly" button at https://zed.dev/, "Incredibly powerful out of the box" section.
Re:Visual Studio Code is designed to fracture on Monday September 30, 2024 @05:33AM (#41695230)
To be honest, Theia (the last beta I tried some months ago) is everything people always complain about Electron apps: slow as molasses - way worse than e.g. Atom (or Pulse) (which VS Code actually isn't).
Re:Visual Studio Code is designed to fracture on Monday September 30, 2024 @05:29AM (#41695209)
I'm sorry, but what _is_ the difference between an editor and an IDE for _you_?

Btw. I'm not saying that having an integrated debugger is a sufficient condition for an editor to be an IDE (VS Code isn't, Sublime Text isn't, other editors with DAP support aren't).

> but don't assume your non-negotiable X is the same for every other user of an IDE. It is not.

But _you_ not needing a debugger in an IDE is a reason something is an IDE without one, I see. Btw. I'm (normally) not using IDEs.

Re:Visual Studio Code is designed to fracture on Monday September 30, 2024 @05:23AM (#41695150)
> I'd be curious what similar caveats may apply to that editor?

Exactly the same as to VS Code, anything that is special about it is "closed" (as a service) https://zed.dev/blog/zed-is-now-open-source

Re:Visual Studio Code is designed to fracture on Monday September 30, 2024 @03:23AM (#41694425)
Everybody can do that themselves, if the original maintainers don't want to (which is a security problem ;):

   If you are not the author, we suggest you first reach out to the author with an issue in their GitHub repo to request that they publish their extension to open-vsx.org. We've drafted a template with suggested content for the issue.
https://github.com/eclipse/openvsx/wiki/Publishing-Extension...

Such "3rd party extensions" don't get the "verified publisher" icon (or at least should not get it ;).

Re:Visual Studio Code is designed to fracture on Monday September 30, 2024 @03:18AM (#41694395)
There are generators for the compilation databases that work with Makefiles and other build systems, like Bear: https://github.com/rizsotto/Bear
Re:Visual Studio Code is designed to fracture on Monday September 30, 2024 @03:14AM (#41694379)
I thought the server part of VS Code (to be exact a proprietary Node addon) is the problem?

https://github.com/VSCodium/vscodium/issues/1229#issuecommen...

Stupid me, the solution is one post below :D

https://github.com/VSCodium/vscodium/issues/1229#issuecommen...

Re:Visual Studio Code is designed to fracture on Monday September 30, 2024 @02:49AM (#41694248)
Yes, their C++ LSP isn't really good and I've heard C# isn't good either - but that's because they want to sell Visual Studio too. But especially "Remote SSH" and "Dev Containers" are so called game changers. And their Typescript and Python extensions are actually good.
Re:Visual Studio Code is designed to fracture on Monday September 30, 2024 @02:43AM (#41694214)
> Zed exists, it's new but it's already a very good IDE.

An IDE needs at least a working Debugger (or, to be more precise, a graphical interface to debugger(s)).

And Zed has exactly the same problems VS Code has, minus actually contributing LSP and DAP (Debug Adapter Protocol) to "the editor community". So, Zed is actually worse in that regard.

Re:Visual Studio Code is designed to fracture on Monday September 30, 2024 @02:33AM (#41694164)
The author forgot about two very important "closed" plugins: "Remote SSH" and "Dev Containers".
Re:Ldd(1) and Untrusted Binaries (2023) on Sunday September 29, 2024 @02:24PM (#41689298)
> strncpy

strncpy had been touted the "safe strcpy alternative" for years.

Re:Ldd(1) and Untrusted Binaries (2023) on Sunday September 29, 2024 @02:21PM (#41689268)
It wasn't meant as an argument against not loading the interpreter, but an explanation why it is "normal" - but if course insecure - behavior for ldd to execute the configured interpreter.
Re:Ldd(1) and Untrusted Binaries (2023) on Sunday September 29, 2024 @02:12PM (#41689199)
Don't know, but on Solaris it's the samé, see section "Security" https://docs.oracle.com/cd/E88353_01/html/E37839/ldd-1.html
Re:Ldd(1) and Untrusted Binaries (2023) on Sunday September 29, 2024 @02:03PM (#41689142)
It's not same, as ldd does print transitive dependencies too. libtree is comparable to ldd
Re:Ldd(1) and Untrusted Binaries (2023) on Sunday September 29, 2024 @01:46PM (#41688986)
Dynamic dlopen calls do not appear in the ELF at all, these are "normal" function calls.
Re:Ldd(1) and Untrusted Binaries (2023) on Sunday September 29, 2024 @01:31PM (#41688888)
It's not about calling the app itself - that doesn't happen with ldd. ldd does not know about dlopened libraries.
Re:Ldd(1) and Untrusted Binaries (2023) on Sunday September 29, 2024 @01:29PM (#41688869)
Each Elf executable can have its own "interpreter" (loader, which as default is `ld-linux. so`), so without calling the configured interpreter ldd can't know about the dependencies of such "special" executables. And the configured interpreter can be any program, AFAIK there are no limititations in the ELF format.
Re:The Design of Text Editors on Sunday September 29, 2024 @02:22AM (#41685310)
But they don't actually work, because there are many ambiguities. Is <= "less than or equal" or an arrow pointing to the left? And in the other direction too: is ≠ "!=" or "/=" or something else? And as soon as you allow 3 or more characters to build ligatures, your number of ligatures explodes, but you still miss some. For example it doesn't matter if <= is an arrow or LTE and => is an arrow, in a <=> all are wrong, same as in a >=> or a >>= or...
I guess that's because it is a VS Code fork.
Re:Eliminating Memory Safety Vulnerabilities at the Source on Thursday September 26, 2024 @02:13AM (#41655071)
> Yeah, but are those bugs security bugs?

If the software is unusable, it doesn't matter if it has security bugs too. Or, to rephrase, the safest software is software nobody uses.

Re:Why I still blog after 15 years on Wednesday September 25, 2024 @11:56AM (#41648791)
> content creation

I seriously hate the term "content" used for "creative output". It is a terrible, derogatory word, that makes me sad. Content is only there to have something to sell, to fill the blank space around ads, the actual content of the content doesn't matter. That people refer to themselves as "content creators" is a sign that they see the value of their creative output only to make money.

Re:How I Built My Blog on Wednesday September 25, 2024 @08:49AM (#41646843)
> However I'd like ask the HN community here to share some examples of really simple blogs?

My static site generator is quite simple (650 lines of JS including the http server, almost half of which are the header and footer templates), it uses markdown-it (and some plugins) to convert Markdown to HTML, Katex to convert Latex to HTML and Highlight.js for syntax highlighting. The generated pages are static, only JS is to change light/dark mode and open all "hints" when printing. And right now I'm adding RSS/Atom support.

https://codeberg.org/Release-Candidate/pages/src/branch/sour... https://codeberg.org/Release-Candidate/pages/src/branch/sour...

The easiest solution would be to allow custom text (with user selectable syntax highlighting).
That's a really fantastic idea, but (yes, sorry ;) there are many fonts missing (I use Fantasque Sans Mono), the syntax highlighting theme should be customisable (at least a light theme) and the source's language should be changeable.

So I always end up using two browser windows of https://www.programmingfonts.org/ side-by-side for comparisons.

Re:Why is F# code so robust and reliable? on Tuesday September 24, 2024 @02:20AM (#41633579)
No, it's not just about lexically scoping, but actually about having to have every (yes, some escape hatches exist like "namespace rec" and "module rec") definition before it's usage, which is an implementation detail of the compiler. So you have to order your files correctly when compiling. Which did break sometimes, because MS' build system/project files doesn't care about order, as C# doesn't care.

Older »