TON surges strongly as upcoming Gram rebrand sparks renewed investor interest.
#Toncoin #TON #GRAM #CryptoNews
https://meyka.com/blog/ton-climbs-15-as-toncoin-ton-set-to-rebrand-into-gram-gram-2606/
TON surges strongly as upcoming Gram rebrand sparks renewed investor interest.
#Toncoin #TON #GRAM #CryptoNews
https://meyka.com/blog/ton-climbs-15-as-toncoin-ton-set-to-rebrand-into-gram-gram-2606/
π€ TON Wallet se mΔnΓ na Wallet DeFi a Toncoin se pΕejmenoval Gram
https://infoek.cz/ton-wallet-se-meni-na-wallet-defi-a-toncoin-se-prejmenoval-gram-2026/
π€ TON Wallet is changing to Wallet DeFi and Toncoin is renamed Gram
https://codeberg.org/GramEditor/gram
The default font selection is a bit le suck, but adjusting to the Noto Sans/Sans Moto and installing the Breeze dark theme makes everything fit nicely into KDE.
In my search for a replacement for VS Code I'm currently looking at Gram, the Zed fork.
https://gram-editor.com/
It's mostly doing the job pretty well, although it obviously doesn't have the same offering of extensions (for better or worse).
One big issue is that it's somewhat locked to LLDB for debugging C++ & friends, and LLDB is really slow on windows for some reason.
Might still run it more on the Linux box though.
Current setup:
IDEs: #Gram Editor @krig Fantastic editor, Zed without the AI crap, more control on your extensions and LSPs.
CLion: The University where I teach makes you choose between Jetbrains or VisualStudio. Not touching MS products so CLion it is.
Current languages:
#Vala by @vala_lang
#Zig by @andrewrk
#python #c #cpp. I'm teaching stuff with these at the University.
Build systems #meson #cmake and #zig depending on the project.
I've been enjoying this arrangement for a while π.
Finished my first day using Gram (Zed fork) as a replacement for VSCode and I think it's already become my daily-driver.
There's GDScript support via a third-party extension, which integrates well with Godot's gdscript server: https://github.com/GDQuest/zed-gdscript
I managed to hack together a #zed / #gram extension to provide FASTA language support:
https://gitlab.com/jrhawley/gram-zed-fastx
https://tree-sitter-fasta.jrhawley.ca/installation/#zed-gram
I tried to write instructions for #lapce but it looks like all languages need to be defined in the Lapce code base for compilation π«€ That puts a damper on that plan.
And #emacs tree-sitter support feels like a moving target. I'd have to manually redefine a lot of font locks and other stuff.
This process isn't as smooth as I'd hoped