HackerTrans
TopNewTrendsCommentsPastAskShowJobs

slbtty

no profile record

Submissions

Java.com Still Recommend Jre8

java.com
3 points·by slbtty·4 lata temu·2 comments

SourceForge: Open-Source Community Awards and Recognition

sourceforge.net
2 points·by slbtty·4 lata temu·2 comments

Haskell for OCaml Programmers

dr-knz.net
5 points·by slbtty·4 lata temu·0 comments

Exiv2 Is Joining KDE

github.com
3 points·by slbtty·4 lata temu·0 comments

Designing Interfaces: Patterns for Effective Interaction Design

designinginterfaces.com
1 points·by slbtty·5 lat temu·0 comments

A GitHub wishlist (from curl's creator: daniel stenberg)

daniel.haxx.se
2 points·by slbtty·5 lat temu·0 comments

C++ 20 versoin header name clashing with VERSION file

github.com
1 points·by slbtty·5 lat temu·0 comments

comments

slbtty
·3 lata temu·discuss
> I think Kate definitely need language servers support

Kate has LSP support for a few years already.
slbtty
·4 lata temu·discuss
Doing exactly the opposite is also a right approach:

Absorb as many features as possible, so that more people will be gravitated into a centralized place. For bugs, if the original feature submitter isn't around, potential new maintainers will emerge and fix them.
slbtty
·4 lata temu·discuss
Jabref, which use .bib file as storage. The importing features are almost the same (all major sources supported). Tagging and note taking are nice. Full text search is implemented with the mighty lucene. Word plugin and Browser import plugin are good too.

Both zotero and jabref are on similar level of simplicity. However, they are very different on details if you use them heavily.
slbtty
·4 lata temu·discuss
It is a gate to the great knowledge.
slbtty
·4 lata temu·discuss
I don't understand why they invest(or buy?) fonts?
slbtty
·4 lata temu·discuss
GNOME is being obsoleted by KDE.
slbtty
·4 lata temu·discuss
There is absolutely nothing that stops anyone from forking the project.
slbtty
·4 lata temu·discuss
They don't even mention a single thing about crypto?
slbtty
·4 lata temu·discuss
The $HOME in unix is a user data storage location

A lot of data is managed by software and by convection there is a dot before them

Unmanaged/Arbitrary data like random pictures or notes are personal and should end up in $HOME/personal

git repos are special managed data, thus they all end up in $HOME/sources

$HOME is supposed to let software to create their data folder and optimally without the dot

The data here includes config (which is read & write like data file)

$HOME/.config or XDG spec is monkey patch that do the wrong thing.

GUI file manager should open $HOME/personal as initial location

Terminal should open $HOME to let user access software's data file with shorter path (aka without .config/ )

You don't know if i am mad or being brilliant or simply brain dead, but i am making perfect scene.
slbtty
·4 lata temu·discuss
The solution is simple, stop messing your home and put personal data in

/home/you/personal/

source code in

/home/you/src/

The home is not a place supposed to store random "regular files"
slbtty
·4 lata temu·discuss
Anti-considered-harmful consided harmful.

What's wrong with the usage? It is short and concise.
slbtty
·4 lata temu·discuss
Why cannot they just recommend java17?
slbtty
·4 lata temu·discuss
The author of this article is the creator of Redis.