Earlier quoted context omitted.
This is my problem. Audio editing on Linux is a joke. For everything else I do, Linux can get me there. So I need a Mac or a PC as an audio editor? Might as well just get a Mac or a PC. I'll have to maintain it anyway, and it can do everything Linux can do, plus probably be better supported.
What about video editing? I mean, I can live with Audacity for my basic needs, but I can't find anything simple as iMovie. Or should I just bite the bullet and learn Blender? Does it have preset screen transitions and stuff like that?
Darling – MacOS translation layer for Linux
171–180 of 274 posts
Re: Darling – MacOS translation layer for Linux
#172Earlier quoted context omitted.
While I agree with your view of HTML+CSS+JS in relation to X and would even go as far as to say the shift towards "webified" apps is (mostly) a good thing, it still saddens me as a developer to see it happening. It's an ecosystem that doesn't discourage lazy practices and it makes me feel unimportant because modern computers can more or less keep up with even the most poorly-written webified apps. I think it's that s…
IMHO the problem is that you actually do need a decent chunk of all that stuff. Not all, but a good chunk. A UI engine is a problem on par with creating a good game engine like Unity. If you don't have a loooooooong list of capabilities and polish your UI is a toy. By the time you extend and build it out enough to make it not a toy you will have re-implemented either Aqua/Cocoa, Microsoft's UI, or the web but yours w…
Regarding security, it seems like something like Servo on top of a capability system like seL4 or Robigalia could provide a lot of opportunity to enhance the client security of a web application.
Using wasm + WebGL (or whatever's in the pipeline for Vulkan) could make this easy to deploy creative applications.
Add IPFS into this mix, and we'll be able to deploy decentralized applications as easily as central-server applications.
I'd like to see better tooling for building UIs on the web before I could get fully behind this idea, but I agree that the web platform has been BY FAR the most successful GUI framework ever, and I say this as someone who works nearly exclusively on systems programming.
Re: Darling – MacOS translation layer for Linux
#173Earlier quoted context omitted.
I go back and forth on whether this would truly be useful. 10-15 years ago, having a fully baked, first class, slavishly source compatible implementation of GNUstep with broad adoption throughout Linux land would have likely been a game changer. But now, it seems webified apps are king. The handful of native apps that people use are already satisfactorily implementable on Linux. In fact, a great number of native apps…
I wrote a blog post once about how the web is the new presentation layer for the desktop, that this is not necessarily a bad thing, and that a desktop OS (e.g. a Linux distro) should just fully embrace it by implementing a desktop that runs 100% via web technologies. Local and remote web apps could coexist as first class citizens, etc. I basically argued that HTML+JS+CSS renderers are the new X and that HTTP(S) is th…
Re: Darling – MacOS translation layer for Linux
#174Earlier quoted context omitted.
The "professional" market doesn't care about visual cohesion. They either use just one app anyway or have them custom written to use their nvidia quadros with whatever UI they like, But the senior execs that need the absolute monster for outlook and facebook will always be well served by the top end macs.
> The "professional" market doesn't care about visual cohesion. That isn't true at all. I spend all day in a handful of applications and good aesthetics make my day much more enjoyable.
Re: Darling – MacOS translation layer for Linux
#175Earlier quoted context omitted.
Is there a list of things missing ? A guide on how to contribute ? I'd love to port my favorite OSX apps to linux (ITerm 2, I miss you so much ;_;) but that website makes it almost a point to be as useless as possible. Also, reading through http://wiki.gnustep.org/index.php/User_Guides , why does it talk about FileSystem Layout. Is GNUStep an OS ? I thought it was just a library. The whole thing feels a bit messy :|.
why does it talk about FileSystem Layout. Is GNUStep an OS ? I thought it was just a library. Pretty much the first thing a desktop environment has to do is establish an abstraction layer for filesystems, so that desktop-enabled applications can have a consistent way to talk about files. Both Gnome and KDE have a VFS layer (GVFS and KIO, respectively).
A good portion of what KIO and GVFS do should be done at a lower level. Instead we get this weird situation where I can "see" a file in KWrite, but I can't see it the shell or in a non-KIO-enabled program.
Re: Darling – MacOS translation layer for Linux
#176Earlier quoted context omitted.
I'd be happy enough if I could run the VM.
Do you mean legally, or at all? Because if it's "at all" I believe there is a very vibrant community who have a lot of tutorials for doing that
* Is it usable for dev work -> yes * Is it like using a mac -> no
Usually When I'm on windows, I generally just run a Ubuntu VM and live inside it.
That is not something you can generally do on an OSX VM.
(just to add, my opinions based on my experience - your milage may wary)
Re: Darling – MacOS translation layer for Linux
#177Earlier quoted context omitted.
> it lacks well designed high quality GUI applications. If porting to Linux was done easier that could change. Fundamental to most peoples complaints about desktop Linux applications is the lack of look and feel cohesion across all permutations of distro, desktop, and toolkit. Wine applications using the Windows APIs look like complete garbage and fit in nowhere. The same would be true of OSX Cocoa apps - they wouldn…
I think a better way to handle this is to show people how to use the command line. That does have a cohesive look and feel and is generally very well behaved compared to nearly anything else. Unfortunately that seems to scare people away so everyone hacks GUIs together to keep them from running and that's how we got to where we are now.
Not really. CLIs can be terribly inconsistent look and feel, even within the same tool (see git), which makes their lack of discoverability even more painful.
Re: Darling – MacOS translation layer for Linux
#178Earlier quoted context omitted.
Wow, that is impressive battery life. I am curious, what Linux distributions you used? (especially for those back in the 90s :D) I was stuck on Gentoo than Arch for the most of the time.
Probably just MakingStuffUp.iso
Re: Darling – MacOS translation layer for Linux
#179Earlier quoted context omitted.
I go back and forth on whether this would truly be useful. 10-15 years ago, having a fully baked, first class, slavishly source compatible implementation of GNUstep with broad adoption throughout Linux land would have likely been a game changer. But now, it seems webified apps are king. The handful of native apps that people use are already satisfactorily implementable on Linux. In fact, a great number of native apps…
> 10-15 years ago, having a fully baked, first class, slavishly source compatible implementation of GNUstep with broad adoption throughout Linux land would have likely been a game changer. I think that GNUstep has actually been around since the mid- or late-90s — but it was never a game changer. I don't know why really ( was it 'fully-baked' and 'first-class'?), although for my part I just never found a reason to use…
If it did, the GNUstep desktop could have gained users (WindowMaker was very popular, me included) and developers would have got interest in it.
That didn't happen.
Re: Darling – MacOS translation layer for Linux
#180iTerm finally!