I don't think Wordpress and VIP belong in the same sentence. There are vastly superior PHP CMS's such as Grav or OctoberCMS that don't make PHP look like a garbage language.
Yes, I completely agree with you! I think being able to read through the actual code of the software you use, in order to fully understand it, what it does, and how it works is a priceless tool. On top of that, most open source tools also provide live examples of implementations, which can be extremely helpful.
However, what do you say to those who will argue that it's actually the other way around? They'll say that private companies have full developments teams paid and dedicated towards maintaining the security of their products... meaning that more work and research gets done, making them more secure, and trustworthy in the end. Or those who say that open sourcing the code makes it easier to find vulnerabilities?
I tried installing this on two different Ubuntu machines using their Ubuntu repo and it did not work. Worked fine on both Android and Ios. This is about what I expect from a java application - the java ecosystem is co convoluted and fragile that the only real options are Android, Ios, and Docker. I wish someone would write something like this in Go or Rust.
To be more precise, ZFS snapshots are mostly just a timestamp reference, similar to how a git commit is just a reference to a git object. Writes don't change the value of the files in the snapshot because they're stored in new places rather than overwriting the existing files on disk.
These are all good ideas. It seems to me part of the problem with these ransom attacks is the intruders aren't pouncing the minute they get inside the victim's network. They take their time, figure out where everything is (including backups) and then only force-spread the ransom malware after they have staged everything just-so.
True, the current Lokomotive repository consists of mostly code forked from Typhoon, something we state in the article. There are a number of small and largish modifications: support for Packet, additional PSPs, etc. But this is just the base Kubernetes portion of Lokomotive. Lokomotive includes 4 main parts, 2 of which have been release thus far. The other public portion of Lokomotive ist the underlying OS, Flatcar Linux. The integration with the recently announced Flatcar Linux Edge channel is the main motivation for releasing at this point; stay tuned for some projects that build on top of this. The other 2 parts will be rolled out this summer. Those are lokoctl, the installer, and Lokomotive Components, a collection of base cluster component.
I find the UX on a Mac to be vastly inferior to Mate or Cinnamon on Linux. The first thing I do when an employer gives me a Macbook is to install Linux on it so I have an usable UI.
By UX I include the touchpad. I have a linux XPS13 and their touch pad isn't comparable to what MacBook Pro provides. Interface on Linux isn't that bad now, I agree, but I like Mac more due to better hardware support and lack of problems.
I agree. And the touchpad is what is stopping me from say, getting a System76 laptop or an XPS13.
I had done some investigation on this before. After all, if System76 is open software and hardware, I should be able to get an add on right?
Not so fast. It seems part of what makes the Mac touchpad so good is a combination of software and hardware.
Microsoft is taking a stab at this. What they had been doing was treating touchpads as a mouse device ... but the hardware gives hints on gestures, so they have been improving their drivers to allow for better experience with the touchpad. (Rather than emulating a mouse device using a touchpad).
The hardware is a bigger block. Apple holds key patents on their touchpad, including the use of textured glass. The glass gives the experience a different feel, but I bet it also smooths out the signals being sent to the software driver. I don't know for sure -- but even say, my Samsung Chromebook, which has a decent touchpad, still doesn't feel the same as my Mac's touchpad.
"More importantly, the patent calls for, in one embodiment, a capacitive track pad with an etched glass surface. Because of its unique properties, and its non-conductive nature, glass allows for high levels of control during the manufacturing process."
"For example, traditional glass has a surface with a high friction coefficient, meaning it resists slippage, making it a less than suitable candidate for trackpad use. However, glass can be made to have a low friction coefficient by etching, sand-blasting, honing, or other methods. This makes the surface smooth and easy to navigate with a finger."
"Traditionally, Windows PC touchpads were implemented in a more one-off way. When you moved your finger across the touchpad, the touchpad driver has to look at the input and convert it to mouse input. The touchpad appears as a normal external mouse—either a USB or PS/2 mouse—to Windows itself. PC manufacturers have to tune the touchpad for their hardware, and the driver is responsible for handling the input. If the touchpad uses multi-finger gestures or has palm rejection support so you don’t accidentally move the cursor while you’re typing, this all has to be implemented by the touchpad driver."
"Microsoft decided to move towards a more standard approach starting with Windows 8.1. It created the “precision touchpad” specification along with touchpad company Synaptics. A PC with a “precision touchpad” doesn’t do all the hard work in its own hardware drivers. Instead, it sends the raw touchpad data to Windows itself. Windows is responsible for reading the input and processing the gestures. Windows understands your PC has a touchpad and approaches it intelligently. The touchpad doesn’t just pretend to be a normal mouse."
Another problem which I include in UX is sleep mode. On Mac it works flawlessly. On XPS13 + Ubuntu/Fedora (I tried both) which I used, there's non zero probability that when I open laptop again, the battery is almost empty.
Check the logs, is it waking, sleeping, waking, sleeping, waking, sleeping? Power management bugs are super annoying because they are tedious to dig into.
In my very obscure case, I got lucky in that suspend was working, then stopped working after a kernel update. Since it was a regression, kernel developers were more interested in tracking down the problem and I was able to find a work around: write PWRB to /proc/acpi/wakeup
The gory details are here, which I expect is so obscure it's not your problem, but shows as tedious as it is, filing bugs with a decently good bug report and willingness to do the work devs need you to do can be worth it.
https://bugzilla.kernel.org/show_bug.cgi?id=185521
I honestly tried my best to debug it. I installed different tools, and at some point it seemed to work, but after some time, due to some updates, it broke down. Some time after this, I just stopped using sleep mode. It was easier to turn on/off the whole machine.
XPS13 which I have is one of the most widely used linux laptops, and it a symptomatic that it doesn't work well.
my xps 13 has no problem going to sleep. It just wakes up slow and drunk sometimes. My "workaround" is to put it into 'performance mode' which kills the battery.
I have not had an issue with sleep mode in Linux since ~2007 or so. (In the early days, it basically didn't work at all)
I've had an XPS 13 9360 for two and a half years now, and an x230 for roughly four years before that. Before then it was a range of cheapo laptops, and while the touchpads and keyboards sucked, sleep mode was fine starting in the late aughts.
I can attest that it took a little while for sleep mode to function at all though. It was a non starter (not intended) in the mid 2000s, but the problems you describe has never been a problem I've had.
At the risk of sounding uncharitable, what is the purpose of your comment? It is hard fact that sleep mode is not a consistently solved problem on Linux. Hardware variations abound, and "works for me on my hardware" isn't very helpful to people with different hardware where it's not as reliable.
As you mentioned, Linux runs on hardware made by hundreds/thousands of different uncoordinated manufacturers. Mac OS runs on a very narrow range of hardware built by the same manufacturer that makes the software. Linux is a very different project to Mac OS.
So take the best examples of Linux machines and compare those with Macbooks. So if eg. Dell XPSes or modern ThinkPad X series have solved the sleep problem consistently then it's fair to compare those with Macbooks.
Of course this doesn't help those people who have trouble with sleep on Linux and hopefully it will get better... but comparing a broad elastic OS running on a vast mess of thousands of different devices with an OS designed specifically for a small range of tightly controlled hardware isn't reasonable. It would make more sense if there were no good examples of decent Linux machines, but this isn't the case.
I'm not making that comparison (I never mention macOS at all); not sure where your reading that. I'm merely pointing out that a response of "it works for me and has for 10+ years" when someone says "it doesn't work on my laptop" is entirely unhelpful.
In fact it shows that they don't at all get the point you've made that Linux runs on orders of magnitude more hardware variants than macOS does and thus it should be obvious that all hardware can't be equally well supported.
I guess it's to demonstrate that it does work on some hardware. I've not experienced any sleep issues worse than what I had on a Macbook. ie, it works 99% of the time.
Right, but I think that demonstration is unnecessary (because, duh, of course it works on some hardware), and entirely unhelpful (because, duh, the person being replied to does have issues with it, and describing an unrelated experience doesn't add anything to the discussion).
I must say that in general sleep mode has been working pretty well for me over the past 10 years in Linux. I had issues on my destop, but tracked it down to a USB headset sometimes not correctly honoring sleep states. I also had a slight problem with one of my laptops when Bluetooth was paired, Bluetooth tended to be broken after coming back from sleep. though I have had more issues my current 2017 MacBook. often when I take it out of my bag after a weekend it will be on 1% battery. it stopped happening around Autumn last year so I think they fixed it.
I have an XPS13, I've changed a kernel command line parameter to change from a soft sleep to a hard sleep and battery life has greatly improved.
The first comment in this reddit thread helped me out.
https://www.reddit.com/r/Dell/comments/8b6eci/xp_13_9370_bat...
