175 karma · joined December 10, 2014
I don't think "bothsideism" exist, the act itself is just a cover up for political opinions. What the accusation of "bothsideism" is actually saying is "you are actually not neutral, but biased". But SP never claimed to be a political neutral medium. It is just some opinionated comedy series that some people enjoys.
The real solution is either find a way to reshape their value or conquer them.
The previous comment did not mention this, instead, it is "Han promised riches for citizens of kaoshung, went to visit China right after the election, and yet haven’t done a single thing yet to improve the city, before running for president.".
What I was saying is that this is not a valid argument.
So you can remind yourself that in hour mind it always seems that "why" matters a lot, but facts matter more than models and models can always be improved. "why"s are supposed to be a friend to guide us, but if they created problems, just be skeptic from and reevaluate the value of question itself.
If your crisis is a "what" crisis rather than "why". It is often easier to cope with, as you only need to open up yourself and remind that all "what" questions are just nomenclature build on immature social/scientific models and never complete. Every "what" question can be altered by a different definition.
People often relate existential crisis with nihilist view, but my opinion is that they are not nihilist enough to think through that the existential questions are meaningless or of low priority themselves.
[edit] typo
The halting problem does not need to be solved, since no program in practice runs forever. In some of the environments like C we don't have a way to specify finite things, where cases would be enumerable and safety guaranteed. To be fearless sometimes greatly reduces the mental workload of programmers and people who read other people's code.
I have a simpler description of the theorem that includes the details:
You can choose 3 out of the 4 things within a axiom system (You can think of it as a language):
1. Completeness: No expressible statement can be neither proved nor disproved.
2. Consistency: There is no statement such that both the statement and its negation are provable from the axioms.
3. The system must be able to describe natural number
4. The system must use formal methods. (The proofs are finitistic)
For mathematicians nowadays, some of them have a natural Platonist mathematics view and take away 4. Some ultrafinilist like Edward Nelson, wants to take away 3. In practical cases we can take away 1, e.g. total functional language.
Some philosophers just wants to take away 2 without justify all the other assumptions.
In terms of moral philosophy, a much simpler alternative to derive the undecidability of nature, Chaos theory, can be used instead of assuming 1, 3, and 4.
The case here, in my view, is much less interesting philosophical than the interpretations of quantum mechanics, where most physicists refuse to discuss.
CSS is originally designed to be a end-user spec language to change the website as they like. But layout is so complicated that it take a lot of experience to define everything in position dynamically as requested.
And now people are using programs (js) to replace the job of CSS, to some extent giving up on writing specs for layout, even with years experience on it.
The hard thing is not the language itself, it is often the domain.
I feel like the points in the article can apply even more broadly to all content, especially the ones that with more "professional" language and good typography, which people naturally tends to trust more, like the Atlantic.
edit: formatting
A codebase of 100% Javascript does not usually mean 100% written by the app developer. If you are coding in react for some basic app, like some basic crud with react using existing backend with Firebase, it almost only require you to learn the some basics of react and Javascript syntax, and fill in the template. You can also use other modules by just follow their documentation when you need some extra functionality.
However in Elm Ports we are required to pass async messages for everything which is much harder. I am OK with the boilerplate for the JSON encoder and stuff, but I have to wrap around my head for how to write a port for lots of basic web APIs.
Port is hard even for people that familiar with Javascript. There are plenty of experienced Javascript programmers willing to dive into the source code of Elm to write native modules to avoid ports even. https://www.reddit.com/r/elm/comments/81bo14/do_we_need_to_m...
In addition, even the 5% of Javascript will eventually leads to the full Javascript stack, where Elm, without an official recommend JS stack, feels more like additional choice as a part of the JS fatigue. Beginners ends up looking up on browserfy/gulp/webpack etc and figuring out a way to integrate Elm in.
> Seems like the argument is Elm isn't ideal if you're not a programmer
I program daily for machine learning, and I have used many programming languages. But Javascript is not the language that I want to dive in too much, which it is the main reason I learn Elm. If your requirement of being a programmer is having a job as a software developer, then I am not. But I think a language with an aim of going into education and scientific computing shouldn't limit itself to that. https://www.youtube.com/watch?v=uGlzRt-FYto
I enjoy Elm. It is one of my favourite programming language. But I have not gotten anything done with it mainly because of ports. If I am pursuing a career in front-end related development, I would dive into Javascript and build stuff. I understand the decisions from Evan and friends and I am just thankful for Elm as it is, there is no right for me to demand anything anyway.
[edit: formatting]
Elm disguised as a beginner friendly language for web front-end, which is not true with the case of ports. Where you need to be fairly familiar with Javascript.
The Elm community also advertise a lot on the advantage of development happiness of Elm over Javascript, and mention the Javascript fatigue a lot. But the truth for a beginner is that you can't escape the Javascript ecosystem when using Elm, and sometimes it requires even more Javascript experience than using just Javascript framework like React to build something that require a web api that's not in the tiny list that Elm provided.
If web development is not someone's main job and they are just finding a tool with better dev experience to build some side projects, the fact that they need to design an interface for almost every external package is not aligned with their original reason to use Elm.
For example in Elm, all the nice error messages can appear next to the line, and all the case-of statements can be auto-completed according to the type definition, it all adds to an overall better coding experience.
However that was all for static UI though. Writing Elm app is still a pain if you are not a Javascript expert. Elm's implementation of the web API is minimal and the progress is extremely slow. In addition, most function that's in libraries in Javascript's ecosystem can not be directly used as you have to write Ports, which requires a lot of Javascript experience.
I wonder what others are? Would like to try them.