And once you're throwing it out, might as well do some experiments.
1,066 karma · joined February 28, 2017
And once you're throwing it out, might as well do some experiments.
I found https://github.com/google/xi-editor/blob/master/doc/plugin.m... , but it doesn't have anything technical (or a tutorial).
I was just being curious as to who would.
What about kernel space?
https://www.reddit.com/r/GooglePixel/comments/7gu5ht/lineage...
Do while the free phone went away (for this in the cell phone market, did plans get any cheaper?) the purchase styles didn't.
It seems more like an "acquired taste" thing that cultured individuals just must enjoy. Like atonal music or rhymeless poetry.
Both Yahoo and AltaVista were started in 95.
I wanted to see how Raspberry Pi assembly worked - quite a niche subject (who programs? In assembly? On a Raspberry Pi?).
Yet I found quite a few blogs going through the subject - a tutorial of sorts.
I was also looking up how to write an OS (just for fun) - another fairly niche field. Yet I found tons of tutorials in C, C++, and Rust.
I remember trying the same in the 1990s.
Nada.
You couldn't find nothing. I mean maybe you'll find a basic site with the source-dump of an OS (often without building instructions), but you want to dig into the meat (here is how you get from bootloader to x86-64 in 21 days, and why it works)? Foggetaboutit.
I definitely don't want to go back to pre-google web1.0.
fun f(a1: Int?, a2: Int?): Int {
if (a1 == null || a2 == null) {
return 0
}
//now you can do something like
return a1+a2
}In contrast, if it didn't, the code would look like:
fn func1(q: Option<i32>, z: Option<i32>) -> i32 {
if let Some(q_in) = q {
if let Some(z_in) = z {
return q_in + z_in
}
}
return 0
}Note the deeply nested parenthesis.
For example, /r/askhistorians requires that all answers be long form and cite peer-reviewed articles (no wiki, first person comments or pop-historians allowed).
Some of the tech subreddits there are much better than StackOverflow - for example, I get better answers on /r/rust than on SO.
I took the "Rust is like C" line to mean is that you can use Rust anywhere you can use C, running at C speeds (the whole zero cost abstraction/no runtime/unsafe blocks), someone that can't be said about OCaml/F#/Haskell (TTBOMK).
EDIT
Moreover, if you look at context, you'll see that his point is that when it comes to OS design, a rust based OS will look mostly like a C based OS.
Now it's "pay X dollars a month 24 months".
What does sf.net have to offer that github (or gitlab which is the "open source not-github github", or bitbucket) doesn't?
For example - compare a Virtual Reality 3D city you can scroll around on your computer, visiting different houses, "chatting" with them, then reading what they posted on their public refrigerator door, then maybe reading some books from their shelf, watch a movie together then you "walk" to a library ... To the internet (Facebook + Wikipedia).
What's cooler? Obviously #1.
What's more usable? #2.
If you could go back in time to the 70s, what would you show on a futuristic movie?
#1, since the you want to "wow" your audience, who won't have to deal with such mundane issues as vertigo, or rapid navigability, or searchability.
But it's not that we can't do #1. We not only could do it, but there were many tries (VRML was supposed to be the "next big thing" since the 90's). It's just that our current UI is better.
[1]. Don't know if you could call them apps, as they needed to be rebuilt with the OS (don't remember if they were pluggable modules or you literally had to rebuild the OS if you wanted to write an App, but it came out of the box with a few apps and games, and you could write your own in C. Their API was weaker than Android's, but to me more enjoyable.)
Now I never looked at Linux code or FreeBSD code (so it really can be that FreeBSD has fewer bugs), but the question is if you will be hit by them.
Application code tends to be the most dangerous code - it tends to not get stringent code review and tends to get less talented engineers relative to kernel engineers. So, in reality, if you use WordPress plugins, Linux security vs FreeBSD security is probably not relevant.
Now let's say you secured your webapp. You wrote it in Rust. Now does it make sense to worry about OS security? Still not necessarily. Really, if you set things up right and apply patches as they come out, the chances of getting hacked are quite slim - is your site worth wasting a zero-day on? And if it is, its likely they'll find a zero-day in FreeBSD (or in nginx, or apache, or ...)
Now comes the million dollar question - where is it easier to apply patches? Linux or FreeBSD? And this is one of Linux's big advantages - RedHat, Ubuntu, and to some degree Debian has a multi-year "stable" track, where you get security, and only security (OK, and non-security bug fixes) upgrades.
Meaning, that its set up that once software is in "stable" (or LTS), its API is locked. If the PHP foundation decides that the future is version 7, I don't have to jump on the bandwagon and rewrite my code. RedHat/CentOS will continue fixing the old release for years.
As a result, you can actually install upgrades unattended (yes, maybe it shouldn't be completely unattended, but you don't have to dread upgrading).
2. You're complaining about windows32 API being slow, but blaming it on .NET ("I don’t know if it was attributed to Windows or the application programmers, but I attributed Windows’ built-in functions with being slow and having shitty PDF output, which is why I refused to use anything related to Win32 or .NET").
Windows API is C (or internally C++).
3. Is display a bottleneck? I never developed GIS applications, but your display is 2D and doesn't have to be real-time. I would assume that the "back end" of the program is doing most of the calculations, and the display just outputs it (not like, say, a 3D game where the rendering engine does a significant chunk of its own work).
The issue with convention over configuration is that you don't see how things should happen, because they're hidden behind the convention.
For example, what are the steps behind your Android build? Can you tell me exactly what steps gradle takes when you run gradlew assembleDebug?
So if for whatever reason you need to modify something, you're completely on your own.
Because, after all is said and done, programming is about having your computer "do" something - whether it be to write some bytes to the disk or to send some bytes to the network.
It's just that sometimes there's an advantage to use an abstraction - such as say "SELECT * FROM TABLE WHERE ROW_ID =14" is an abstraction over something like "for (int i =0;i<table.size();i++) if(table.row[i].elem[1] == 14) ... ", but often you don't need such a complicated abstraction, you just "need something done" before (or after) building. Whether it be that you want to download an HTML file to package, or to move the resulting file to a certain directory, or to clean a certain directory, your build language shouldn't be that arcane that you have to create a "build.sh" to get things done.
The bigger danger is the response by android developers. Will you invest in a soon-to-be-deprecated Android Native app written in a soon-to-be-deprecated API (because, at least according to the Internet rumors, Fuchsia will be using Dart instead of Java and will have a totally different API), rather than just write it in Xamarin, Cordova or React Native?
And once your apps aren't written in Android API, how hard is it to port to, say, Windows Phone?
This damages their moat.
That's the free rider problem, one that the GPL (and the AGPL) was designed to avoid.
It's true that many of those companies which use FreeBSD wouldn't touch a GPL codebase (and all the more so an AGPL codebase), but that't the point - while some chose FreeBSD because it's fast/stable (NF and WhatsApp), others chose it because they don't have to contribute back.
For example, I have an app that has a vulnerability (let's say my alarm app accidentally runs unauthorized code). What can it do? Nothing. It can't read from my banking app, it can't get my SSH keys, it may not even be able to read from my SD card.
But what happens when my Linux kernel is also compromised? Any app can get root.
Just to point out, that DTrace and ZFS are (were) not BSD features, and were not invented by a Open Source BSD.
It just happened that they were open sourced by a GPL incompatible license (CDDL) which makes it impossible to directly merge it into the mainline Linux kernel.
EDIT
Just also to point out that had ZFS been a BSD licensed tech, it's very likely that ZoL would have been just as good an option as ZFS on FreeBSD.