Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Switching from macOS: The Basics

blog.elementary.io

Post reply on HN
Print view View original

121–130 of 610 posts

Re: Switching from macOS: The Basics

#121

Post by pjmlp »

kristopolous wrote: post #104
pjmlp wrote: post #77

Earlier quoted context omitted.

Not really. GNU/Linux doesn't have desktop stack capable of matching Objective-C, Swift frameworks both in feature set and related GUI tooling.

How thorough of a survey have you done?

I have used Gtk+, wxWidgets, Qt, KDeveloper, once upon a time between 1995 and around 2004.

Still use GNU/Linux on my travel netbook and of course, some of our servers run it. Last time I used Qt in anger was 5.3, while trying to do a mobile project that I eventually ported to pure native APIs.

Do you know of any other frameworks, besides those that cover all of these ones?

https://developer.apple.com/reference/

Re: Switching from macOS: The Basics

#122

Post by aorth »

krzyk wrote: post #48
aorth wrote: post #34

Earlier quoted context omitted.

But privacy != security. Chrome implements the most security mitigations compared to all other browsers.

Do you any source to back that up? This is the first time I hear something like that.

It's well known in the information security community for years. But here's a recent article on grading software security like how we grade cars:

https://theintercept.com/2016/07/29/a-famed-hacker-is-gradin...

They give one example (with a graph) of the security mitigations that are in popular web browsers:

https://prod01-cdn07.cdn.firstlook.org/wp-uploads/sites/1/20...

Firefox scored below Chrome and Safari in several areas: address space layout randomization (ASLR), heap protection, stack guards, fortified source. And I've even seen infosec people saying that Firefox has some of these, but doesn't even enable them on builds for some platforms!

Re: Switching from macOS: The Basics

#123

Post by eloisant »

FrankBlack wrote: post #47

Perhaps I am just dense, but the article references, specifically, the "Pro" market. For most pros that I know (and I am among them), our OS choice is often based on our tools, not the other way around. If I need Photoshop, Lightroom, Logic Pro, Visual Studio, etc., switching will be quite a chore. For the average user, this is probably a much more appealing argument.

Yes, even for a developer looking to switch from OSX to Linux, it's much more relevant to discuss how he will be working with his usual tools (git, IDE/editor, installing with apt-get, docker, etc) than whether the dock or the notification bar will behave the same as on OSX.

Re: Switching from macOS: The Basics

#124

Post by haffla »

I find Apricity OS (Arch Linux) much better suited for developers. In fact at work I switched from Ubuntu to Apricity. Through yaourt (paceman frontend) and AUR (Arch User Repository) it's a breeze to install the latest versions of literally everything you need be it Docker, Java or IntelliJ. I think it's comparable with brew. Plus Apricity looks so much better than Elementary in my opinion and almost manages to give you that macOS feeling.

Re: Switching from macOS: The Basics

#125

Post by hugs »

FrankBlack wrote: post #47

Perhaps I am just dense, but the article references, specifically, the "Pro" market. For most pros that I know (and I am among them), our OS choice is often based on our tools, not the other way around. If I need Photoshop, Lightroom, Logic Pro, Visual Studio, etc., switching will be quite a chore. For the average user, this is probably a much more appealing argument.

There are also pros who primarily do web development. They need a terminal window, a text editor, and a web browser -- making switching to a different platform not as painful.

Re: Switching from macOS: The Basics

#126

Post by matzipan »

rvschuilenburg wrote: post #25
aorth wrote: post #15

Yes, the Elementary team has been doing great work for years. Sad that it's all parallel to the efforts of the larger GNOME Desktop project. I don't know how much code gets shared between the two, but I cringe to think that Elementary is dragging along a suitcase full of patches! Some of their apps are forks, while others are written from scratch to fit their design (UI/UX/simplicity) goals. I think their decision to…

> I think their decision to use what amounts to a random, third-party web browser (Midori) as the default is laughable They switched to the default GNOME browser "Epiphany" in the latest release of elementary OS. But I agree, the first thing i did was install a different browser. In my case Firefox.

The version of Epiphany which has to ship with Ubuntu (because Ubuntu is only shipping GTK 3.18) is pretty outdated [1]. I have been trying to move away from Chrome to Epiphany slowly but was encountering quite a few issues which I reported to GNOME and they were like "Oh yeah, we fixed this a long time ago, get the latest version".

I got the latest version via flatpak and I've completely replaced Chrome. There are still a few issues to be ironed out in flatpak (like notifications and downloads support), but it's getting there!

[1] https://blogs.gnome.org/mcatanzaro/2016/03/30/positive-progr...

Re: Switching from macOS: The Basics

#127

Post by pjmlp »

pmlnr wrote: post #109
pjmlp wrote: post #77

Earlier quoted context omitted.

Not really. GNU/Linux doesn't have desktop stack capable of matching Objective-C, Swift frameworks both in feature set and related GUI tooling.

GTK? QT? And, since we're talking elementary, Vala?

Not really, they don't even cover half of these ones

https://developer.apple.com/reference/

Not to mention the related GUI tooling.

Where is Instruments on QtCreator, for example.

Re: Switching from macOS: The Basics

#128

Post by coldtea »

deadbunny wrote: post #113
pjmlp wrote: post #77

Earlier quoted context omitted.

Not really. GNU/Linux doesn't have desktop stack capable of matching Objective-C, Swift frameworks both in feature set and related GUI tooling.

Because most people using linux on the desktop (thus the development target) value functionality over aesthetics. Do I like it when things are pretty? Sure. Do I need them to be pretty to get shit done? No

>value functionality over aesthetics.

Not much in that department, either. Nothing that beats the proprietary software staples, especially for creatives, that I happen to use: no Cubase, Pro Tools, Photoshop, Premiere, etc. Lots of apps ranging from "close but no cigar" to "why even try?".

Re: Switching from macOS: The Basics

#129

Post by divanvisagie »

oneeyedpigeon wrote: post #88
tambourine_man wrote: post #22

Unfortunately, no Photoshop, no go

I feel like, unless your situation dictates a specific product (which is unlikely), this should be rephrased "Unfortunately, no graphics editor that does x, y, z". If you continue to put up a 'Photoshop' barrier, then you will never be able to consider any alternatives — assume Photoshop will never happen on Linux, but that there may well be a graphics tool in future that is far superior as far as your needs are conc…

Not really, The functionality required is "Everything photoshop does" I think the problem with the Linux desktop is that everyone thinks its fine and blames users for being dumb instead of providing a better experience.

As an engineer part of your skill is trying to translate what people are saying into something meaningful

Post reply on HN