News for hackers. Stuff that matters.
Re:We need to document macOS by stuntkite on Sunday August 13, 2017 @07:07AM (#15002437)
I bought Windows 10 Pro last year and had really high hopes for it after the Ubuntu shim was introduced. Windows is a fucking nightmare for anything involving producing audio at a pro level. The Ubuntu shim does not solve what I need even though it's a nice add. The real kicker is that STILL many errors produce a window where I can't even fucking copy the output. Why that is still a feature, I have no idea. That coupled with how they manage fixes/updates and a general distrust for the system being close to secure... It just didn't work out.

I wanted to buy that giant drafting table computer with the knob and say fuck it to the MBP. I went to look at it and bought another kinect one day, and what felt like an omen, their windows run point of sale system that tries to hide in the desks like the apple store failed so bad at taking my card that the guy had to use two different work stations and literally was "turning it off and on again" with both his card swiping windows mobile phone and the computers.

I feel like my future is in some sort of hand rolled main LXD or CoreOS or the like, that quickly composts whole systems locally and in the cloud but also easily remote desktops to local Mac and Windows machines. I have ideas in my head and a bit in code for a bare bones graphical interface that renders a graph that I can attach arbitrary points to that go to systems, API, terminal instances, containers, etc. I can weight the node connections and also record weight on paths based on frequency of traversal enabling automatic access shortcuts. Of course OSX is close to impossible to run virtualized, which is stupid as hell. Actually if it could without a larger time investment than my full time job that might solve all of my problems.

I don't know, I still need all of the systems that are out there... but I think it's time to put a top layer interface on it that gives me them and more. Setting up a springboard for something that doesn't sit around waiting for big providers to bless me with mana from heaven while they wave their dicks in my face.

Here's an example of a nerfed version of what I'm talking about as an OS supervisor UI that I'm using for a lesson series on Docker [https://www.dropbox.com/s/be4lh1015y305jr]. There is nothing about it that's clean or safe to operate, but I just wanted to prove it. In the current version you can select a node and drop to a terminal inside of a container. Also, I've added support for API nodes auto generated from graphql and REST (if you write the schema). I think it proves the concept. The next step is the pullback to whole systems I guess.

Re:We need to document macOS by anonymfus on Sunday August 13, 2017 @08:34AM (#15002658)
> The real kicker is that STILL many errors produce a window where I can't even fucking copy the output. Why that is still a feature, I have no idea.

BTW a standard way to do it is to just press Ctrl+C in such window without any text selection or context menu. Because such messages could be shown when system has no resources to create context menu or text selection, and that was very important in 16-bit days.

Re:We need to document macOS by delinka on Sunday August 13, 2017 @08:48AM (#15002695)
Let me klingon to the thread with this:

It's 2017 and I still can't use the keyboard to copy and paste from and to a Windows command line window...

Re:We need to document macOS by hungerstrike on Sunday August 13, 2017 @11:03AM (#15003166)
Yes you can. Try it out.

Windows has better keyboard accessibility than any other desktop OS.

Re:We need to document macOS by DanBC on Sunday August 13, 2017 @08:50AM (#15002702)
Ctrl C and Ctrl V works in Windows 10 command prompt.
Re:We need to document macOS by stuntkite on Sunday August 13, 2017 @09:07AM (#15002751)
Also if you're not quite ready to kill yourself while using the windows command prompt. Enjoy a powershell.
Re:We need to document macOS by rpeden on Sunday August 13, 2017 @09:25AM (#15002808)
You'd probably enjoy Cmder[1]. Everything works really nicely, it supports multiple tabs, and you can download a version that includes most of the Unix commands you know and love.

[1] http://cmder.net/

Re:We need to document macOS by majewsky on Sunday August 13, 2017 @05:00PM (#15004904)
> you can download a version that includes most of the Unix commands you know and love

Is it the actual Unix commands that I actually know and love, or just 25-year-old parodies like on macOS? (I've stopped keeping track of how often my bash scripts broke on macOS because I was giving some switch to a coreutil that was introduced less than 25 years ago.)

Re:We need to document macOS by krallja on Sunday August 13, 2017 @10:52AM (#15003108)
Alt+Space E P
Re:We need to document macOS by stuntkite on Sunday August 13, 2017 @08:47AM (#15002689)
I'm sure your right. The fact that they haven't updated that and I've been in *nix/OSX for 8 years now made my frustration point maybe lower than it should have been. Then the next thing I'm doing is trying to use cmd and powershell and my hair falls out.

But this is great info and will definitely keep be from cursing quite as much next time I'm MS admining.

Re:We need to document macOS by Roboprog on Sunday August 13, 2017 @02:42PM (#15004243)
I hear you about the audio part. I do electronic music as a hobby - I'm not much of a keyboard player, but I do a lot of editing and tweaking using a digital audio workstation program (DAW).

Whenever I look for stuff in user forums, it seems like it's always the folks on Windows who are having a devil of a time getting audio drivers and stuff to play nice. I can't imagine dealing with all of the nagware popups and such on Windows, either, when trying to run a song. Sounds like the kiss of death if you were ever performing.

I have been using Linux since 1995, but switched over to OSX (Macs) about 5 years ago. Commercial audio products generally don't work on Linux. Maybe you can get Reaper to work under WINE, but good luck getting any licensed soft-synths to run (maybe, but I never tried). I'm sure you can "muzzle" some of Windows more annoying nagging and such, but I have other things to do than get an MSCE cert - paying triple for a laptop to Apple every 5 years or so turns out to be cheaper and faster than keeping up with MS internals :-(

Back to the main topic: I've developed a vested interest in the last few years of seeing OSX continue to thrive. I hope Apple doesn't kill it by continuing to make reckless changes to the hardware and/or software.

Re:We need to document macOS by mmjaa on Thursday August 17, 2017 @11:57AM (#15037911)
FWIW, Ubuntu Studio rocks for audio guys.