Live data from Hacker News

Inkscape 1.2 released

inkscape.org

111–120 of 233 posts

Re: Inkscape 1.2 released

#111
post #19

Great to see the project moving along, but it's been a persistent feeling of mine that FOSS is starting to get left behind in the dust. The design space has been very rapidly moving towards online, live collaboration tools like Figma, Sketch, Adobe XD, etc and FOSS just has no answer for this market. Even a lot of the big name proprietary tools are finding themselves becoming rapidly obsolete in a world where people…

Good employees find ways to collaborate no matter what. That’s to say that real-time collaboration is a luxury feature. Also, many projects have only one designer. Not to mention, it’s rare to find designers that work in tandem. Also, from a dev perspective having designs updates without some process is undesirable.

On my deathbed, I doubt I will be regretting not bending my life out of shape more so someone would call me a 'good employee'.

Re: Inkscape 1.2 released

#112

Great to see the project moving along, but it's been a persistent feeling of mine that FOSS is starting to get left behind in the dust. The design space has been very rapidly moving towards online, live collaboration tools like Figma, Sketch, Adobe XD, etc and FOSS just has no answer for this market. Even a lot of the big name proprietary tools are finding themselves becoming rapidly obsolete in a world where people…

Have you had a look at Penpot?

https://penpot.app/

From the same team as Taiga:

https://www.taiga.io/

Re: Inkscape 1.2 released

#113

Great to see the project moving along, but it's been a persistent feeling of mine that FOSS is starting to get left behind in the dust. The design space has been very rapidly moving towards online, live collaboration tools like Figma, Sketch, Adobe XD, etc and FOSS just has no answer for this market. Even a lot of the big name proprietary tools are finding themselves becoming rapidly obsolete in a world where people…

> FOSS just has no answer for this market

And thank god for that.

Users literally hate the Adobe model, but aren't given a choice.

Please remember what the 'F' in FOSS stands for. Hint: it's not about money.

Re: Inkscape 1.2 released

#114

Great to see the project moving along, but it's been a persistent feeling of mine that FOSS is starting to get left behind in the dust. The design space has been very rapidly moving towards online, live collaboration tools like Figma, Sketch, Adobe XD, etc and FOSS just has no answer for this market. Even a lot of the big name proprietary tools are finding themselves becoming rapidly obsolete in a world where people…

Sorry your use case isn't being met, but it's hardly the point of inkscape to become a saas. The typical use is, "I need to draw something on my PC."

Yep, exactly. It's absolutely insane we've now reached for a point where when people see a standalone, working, polished piece of software that respects your freedom, they somehow feel that it is "inferior" because it doesn't take away your rights.

I, for one, am glad that Free/Libre software like inkscape continues to be heading strong, and find that it far outpaces any of the proprietary malware SAAS applications out there.

Re: Inkscape 1.2 released

#115
Amazing, just two days ago I was searching for a polar arrangement tool in Inkscape. FOSS tools are often worse from a UI/UX perspective, sure, but I contend that they usually provide something consumer commercial tools often don't: respect for users. I'm not necessarily talking about welcoming communities here - respect can take the form of, say, not engaging in hostilities like: - The sword of Damocles that is renting software. Can't pay? Can't access your data. Or worse, it's gone. - Developed-country-centric pricing models/heavy focus on newer hardware. - Locking you out of creative uses of the software - either our way or the highway - Effectively forced TOS or pricing changes - Unexplained bans/AI moderation/guilt by association/becoming subject to laws not relevant to your jurisdiction - Forced upgrades breaking workflows or removing features - Corporate bankruptcy/"amazing journey"/sales/pivots/mergers/etc ruining your investment - Misfeatures such as nag screens, dark patterns, engagement boosters (time wasters), unclear data collection... - Opaque bug submission channels, limited to no access to the engineers building the thing - Optimizing for revenue, not usefulness

There is a feature count/learning curve price for this, I will readily admit. Sometimes, untenably so. My claim is simply that FOSS tools are important as a backstop/foundation.

I feel that any problem solved exclusively by proprietary software is only solved temporarily and for a tiny percentage of the world population. If the company goes away or the IP otherwise becomes inactive, that's it. Especially with cloud software. With FOSS, the software never really goes away. The problem mostly stays solved, and anyone can resume the work if they are willing and able. I'd imagine a forked FOSS version of Win2k, VB6, or maybe the late-2000s Google indexer (bit of a stretch) would be quite successful today, for example. Guess I'll never be sure of that.

Just musing after a beer and some Red Vines - I welcome any criticism or kindred spirits.

Re: Inkscape 1.2 released

#116
post #9

I want to like Inkscape, but the macOS version seems sluggish and buggy.

When I criticised this on twitter one of devs started replying and getting upset at me. He couldn’t understand that I don’t want to use a piece of software that runs at 5fps

Re: Inkscape 1.2 released

#117

I will be very happy if one day I open up Inkscape and I'm not presented with a virtual sheet of paper as my starting point. I find it extraordinarily off putting to have to pretend I'm going to print out the end result.

I really like Affinity Designers art board feature for this

Re: Inkscape 1.2 released

#118
post #43

Here is a link to the release video: https://www.youtube.com/watch?v=1U4hVbvRr_g

Would also highlight Martin Owens' Video: https://www.youtube.com/watch?v=TMHnyL4cRYA

He has been consistently putting out videos on his process and has been a (the?) main driving force behind the new pages addition.

He's also on patreon: https://www.patreon.com/doctormo

Re: Inkscape 1.2 released

#119
post #94

Earlier quoted context omitted.

Sort of, but it's not the whole story. They do use cairo for rendering to a CGContext via cairo_quartz_surface_t which has traditionally not been all that great on macOS. Additionally they're dealing with colorspace transforms on more recent macOS along with some bugs in macOS that were causing non-native applications to do considerable damage/redraws. If/when Inkscape moves to GTK 4, a lot of this will just go away.…

Thanks for your efforts, I'm really pleasantly surprised to hear there is work to improve the GTK 4 experience on non-Linux platforms. Does this port support the native macOS window decorations, or are they client-drawn?

Both, but it's up to the application to choose what they want on whichever particular platform they're targeting by using gtk_window_set_decorated().

I have some blog posts from the effort to write the new backends which gives some additional details.

https://blogs.gnome.org/chergert/2022/02/14/modernizing-gtks...

https://blogs.gnome.org/chergert/2020/12/15/gtk-4-got-a-new-...

https://blogs.gnome.org/chergert/2021/02/24/gtk-4-ngl-render...

Re: Inkscape 1.2 released

#120
post #101
post #89

Earlier quoted context omitted.

That’s exactly the problem; Google Docs’ use case is only “share a basic document and collaborate on the words.” It’s not capable of creating precise or maintainable documents (e.g. no styles as others have mentioned), which is a very common need that it’s adjacent enough to that lots of people use it for and then it fails.

What is a style? Are you trying to create a poster or do some graphic design? Some weird xml style sheet thing? Yes it’s not for that, but then also doing that in libre office or word also sounds horrible and unmaintainable.

To define a custom style in a word processing context means to define "a group of settings that I can apply at will to parts of the text".

That is, I should be able to define a "Code block" style that should appear in the same dropdown where google docs lets you select heading levels. When I select that "Code block" style, the app should format the selected bit of text according to the syte's definition. For instance: use a monospace typeface, apply some margins to this paragraph and paint a gray background on it.

Likewise, I should be able to update the style definition and all code blocks should update accordingly.

This is very basic functionality that has existed in word processors since... forever. Large and/or more complex documents are simply much much more painful to maintain/evolve without this feature.

Post reply on HN