[-] [email protected] 3 points 2 hours ago

IDS only got in because the labour vote got split between the newly added labour candidate and the one who got disowned by the party

[-] [email protected] 1 points 5 days ago

Not counting my "fancy" tea - loose leaf stuff etc. I always default to Twinings English Breakfast.

[-] [email protected] 26 points 1 week ago* (last edited 1 week ago)

There is a difference between censorship and the right to not have to listen to somebody. Being banned from having a platform to speak from could count as censorship (for example being banned from Reddit). However with Lemmy those on lemmygrad are free to say whatever they want, the difference is that everyone else is just as free to not have to listen. The idea of the Lemmy instances is that they have the ability to curate content - an instance catering to an LGBT community is not going to want to have to listen to right wing evangelicals and you join up on that knowledge. If you want to have the option to hear every single voice then join an instance with that mindset or just host your own.

[-] [email protected] 42 points 1 week ago* (last edited 1 week ago)

From the conversation it seems to be a similar situation to the project I'm with is in. The flatpak is essentially community maintained rather than being directly supported by the team. To become verified it needs to be done so by a representative of the maintainers of the software. To be verified it doesn't have to have a team member involved in it but this is a requirement Inkscape seem to have imposed.

For us we just aren't in a position to want to support it officially just yet, we have some major upgrades coming to our underlying tech stack that will introduce a whole bunch of stuff that will allow various XDG portals etc. to work properly with the Flatpak sandboxing model. To support it now would involve tons of workarounds which would need to be removed later.

[-] [email protected] 46 points 1 week ago

The moment you exclude any group or persons from your licence, it is, by definition, no longer open source.

Of course that doesn't sit well with some people and there are some initiatives to try to account for that, for example the Hippocratic License that allows you to customise your licence to specifically exclude groups that might use your software to cause harm or the Do No Harm license with similar goals.

Honestly, I find it hard to object to the idea. Some might argue it is a slippery slope away from the ideals of software freedom (as has been the case with some of the contraversial licenses recently like BSL and Hashicorp. I'm not a hardline idealist in the same way and if these more restrictive licenses that restrict some freedoms still produce software that might otherwise not exist then I'm happy they are around.

Would I use one? Probably not, for me, whilst I like the idea, I think the controversy generated by using a non-standard licence would become its defining feature and would put off a lot of people from contributing to the project.

10
submitted 2 weeks ago* (last edited 2 weeks ago) by [email protected] to c/[email protected]

Get your grills ready, Pulsar v1.118.0 is cooking with gas! With lots of love to syntax highlighting, along with a zesty sprinkling of features and fixes. We've got Tree-sitter fixes and improvements from query tests, better documentation of our Tree-sitter usage, an updated PHP parser, and loads of improvements to Clojure, there should be a little something for everyone. But of course feel free to dive into the changelog for further details.

[-] [email protected] 39 points 3 weeks ago* (last edited 3 weeks ago)

I think a lot of the flak directed towards snap would be mitigated if they made the backend open source. I know there are some efforts to produce alternative backends (although the one I knew about lol / lol-server seems to have gone dark).

Another issue is Canonical's rather strong armed and forceful approach to making people use snaps rather than the OSs native packaging system, again, not something that should be an issue in theory but when people already have a negative view of the format to start with...

Personally I don't really have an issue with Snaps. I've had more luck with them and fewer issues than Flatpaks (which I also tend to avoid like the plague) but that is probably just because I prefer to use appimages or native packages rather than having to fight the sandbox permissions and weird things it can do to apps that don't take Snaps and Flatpaks properly into account.

8
submitted 3 months ago by [email protected] to c/[email protected]

A week later than you’re accustomed to — but worth the wait! Pulsar 1.115.0 is available now!

Last month’s 1.114.0 release was full of fixes related to the recent migration to modern Tree-sitter. This month’s release is much smaller, but still dominated by Tree-sitter fixes affecting syntax highlighting, code folding, and indentation.

7
submitted 4 months ago by [email protected] to c/[email protected]

Welcome to a brand new Pulsar release!This release features a lot of updates and fixes for our modern Tree-sitter implementation, an assorted bag of bug fixes and some new features to introduce, such as restoring compatibility with older Linux distributions and a new ppm command.

5
submitted 5 months ago by [email protected] to c/[email protected]

Last month was our biggest update to Pulsar we have had in quite a while, so in this blog we will be addressing some of the issues people have seen and what you can expect in terms of fixes and updates. Outside of that, we have some big changes to the Pulsar Package Registry backend that give (and document) a bunch of new filters and endpoints to the API, as well as a reminder for @maurício szabo's blog post detailing our biggest hurdle: the road to modern versions of Electron.

[-] [email protected] 36 points 5 months ago

A bit of gratuitous self promotion but just to let people know if you liked Atom and are still using it or maybe you migrated to a new editor and still miss Atom, it was forked as Pulsar which is entirely community-led and is seeing a lot of active development to bring it up to date. We also have a lemmy community at [email protected]

[-] [email protected] 49 points 5 months ago* (last edited 5 months ago)

This is the problem, making the fork known to the userbase of the original software. When the Atom text editor was killed by Microsoft we decided to fork it as Pulsar but it was an uphill struggle to really get the word out. We got a massive boost when the youtuber Distrotube featured us in an episode and again with an itsfoss article but we still routinely find people who have been using Atom without knowing we even exist.

8
submitted 5 months ago by [email protected] to c/[email protected]

In the beginning, Atom appeared. It created an API to make packages, but together with this API, it also allowed authors to use web APIs together with node.js packages, modules (including "native modules" - more on that later) and, finally, a special API that was used to communicate between the "main module" and the "browser part".

That last part, eventually, split from Atom and became Electron. And for a while, the Atom development was tied to the Electron one, meaning that an update on Atom usually meant an update on Electron, and vice-versa.

Unfortunately, that wasn't the case for a long time...

4
submitted 5 months ago by [email protected] to c/[email protected]

We’ve been telling a series of stories about all the different ways that Tree-sitter can improve the editing experience in Pulsar. Today’s story about symbols-view starts a bit slowly, but it’s got a great ending: the addition of a major new feature to Pulsar 1.113.

[-] [email protected] 43 points 5 months ago

Somewhat self promoting for the first two of these items as I'm directly involved. Leaving out the more obvious ones (Linux distro etc.) as they will have been mentioned. I'll stick to some of the less known things I use.

10
submitted 5 months ago by [email protected] to c/[email protected]

Welcome to the release of Pulsar 1.113.0, our first release of 2024. For this release we have enabled our modern Tree-sitter implementation by default, a new Tree-sitter PHP grammar, a huge update to our 'symbols-view' package, a bunch of bug fixes and an issue where we banish 😡 to the Netherrealm.

3
January Community Update! (pulsar-edit.dev)
submitted 5 months ago by [email protected] to c/[email protected]

Welcome to our first community update of 2024! We have a reminder about our upcoming tree-sitter change, a resolution to our annoying website issues, a brand new PPR API endpoint so you can find packages by your favourite authors, a statement on our commitment to our long-term projects and a very special new year community spotlight.

2
submitted 6 months ago by [email protected] to c/[email protected]

Welcome to our 12th regular release! It has been exactly a year since we put out our first tagged release and development continues. This month we have some new soft-wrapping options, some long overdue updates to PPM, improvements to our "GitHub" package, a new fuzzyMatcher API and our usual slew of bug fixes.

6
submitted 6 months ago by [email protected] to c/[email protected]

This month we have a big update on our plans to move to a new version of electron and what that might mean for our releases, some better error handling on our package website and our usual community spotlight to say thank you to those community members contributing to Pulsar's development!

3
submitted 7 months ago by [email protected] to c/[email protected]

Welcome to a new Pulsar regular release!

This time we have a brand new API, a reduction in Pulsar's installed size, a fix for a really tricky and annoying bug, and some fixes from the community.

3
submitted 7 months ago by [email protected] to c/[email protected]

One annoying thing that software developers do is insist on writing in more than one language at once. Web developers are espeically obnoxious about this — routinely, for instance, putting CSS inside their HTML, or HTML inside their JavaScript, or CSS inside their HTML inside their JavaScript.

Code editors like Pulsar need to roll with this, so today we’ll talk about how the modern Tree-sitter system handles what we call injections.

[-] [email protected] 27 points 10 months ago

It isn't quite correct. Darwin is actually an open source operating system at the heart of macOS which is based mostly on a bunch of BSD and nextstep stuff. The actual kernel is XNU, based on the Mach kernel.

[-] [email protected] 164 points 11 months ago

Oh god, have we really come around to screenshotting bash.org?

[-] [email protected] 30 points 1 year ago* (last edited 1 year ago)

I find this a very odd take... You are free to say whatever you want, however people are also free to not listen to you. Why is the freedom to not listen seen as a "lesser" freedom than the freedom to say what you want?

The main benefit of federation like Mastodon and Lemmy is that if you and like-minded people in your community don't wish to listen to vitriol being spewed then you don't have to. Don't like it? Go and find an instance that does tolerate it and does want to listen.

view more: next ›

Daeraxa

joined 1 year ago
MODERATOR OF