Sure, everthing else is a piece of cake. 
-
-
-
Hey I worked on Rails 3, help maintain a Rails app, am a member of the Rust core team, manage a Rust agent for
@skylight. I'm not saying the other stuff is easy. I'm saying front end is hard in underappreciated ways. -
Ah - this is much better, otherwise I would strongly disagree, because each "layer" has its challenges, but Frontend might - at least for non UI/UX folks - not seen as important as other disciplines.
-
WHOOPS! I actually followed up here:https://twitter.com/wycats/status/930489573850857472 …
End of conversation
New conversation -
-
-
Agree that front end is underappreciated and difficult. It's not fair to call most front end real-time. Unless your primary problem space is preemption, priority, and deadline it's not really real-time. Responsive or consistent would be more appropriate IMO.
-
Real time in this sense means: - very sharp deadlines for downloading and running (compared to native apps which can get away with asking you to download many megabytes) - taking actions in the browser can't take long enough to block the main thread or scrolling fails.
-
I sometimes use "soft realtime" in this formulation, which I think is completely accurate. "A system is said to be real-time if the total correctness of an operation depends not only upon its logical correctness, but also upon the time in which it is performed."pic.twitter.com/G2aCYvkBVj
End of conversation
New conversation -
-
-
Aw, thanks. That means a lot coming from you. Frontend engineers sometimes have chips on our shoulders because we face the constant attitude that what we are doing isn't Real Programming™.
-
I know the feeling. I work on a lot of backend stuff (including rust) and find that people underappreciate front end.
-
The largest irony is that many of the "full stack" developers only work with 1-2 programming languages on the back-end.
-
I always thought full-stack meant you did frontend and a bit of dev ops, too. Either that or it’s a nearly meaningless we use in place of “I know lots of stuff about computers.”
-
I think it usually means "I do everything needed to ship an app end to end" which means backend, front-end and enough devops (but could mean experience with a particular PaaS). It's pretty hard too ;)
-
It can also mean: I am calling myself this because that's what your job description asked for and I am interested in working for your company.
End of conversation
New conversation -
-
-
As someone who does both on equal ratio, I can say backend is harder and consumes more time. Backend asynchronous message communication over TCP where every async state & dc needs to be handled correctly, ugh. Frontend is fun though. 60 fps is also much easier nowadays.
-
Do you do backend on the bare metal? Stateless backends (the dominant kind) are simpler than almost any front end web app. And front ends have to work harder to keep deps and size small.
-
Frontend taking a lot of deps is the developer's own fault, not the fault of frontend development per se. I write my frontends with 0 deps and it's working perfectly for me. People use too many 3rd party libs slowing everything down.
-
Keeping the number of deps small is what I'm saying makes it harder (you can more freely use deps on the backend)
- 1 more reply
New conversation -
-
-
What makes it even harder is the nature of underlying tech, no one has been able to make a perfect JS framework yet, JS<->DOM somehow seem incompatible. The closest anyone really came to solving the issue is by going diametrically opposite like React or Elm.
-
I don't think this is quite right but it's more parochial than the point I was trying to make :) I don't think "programming model mismatches" are quite as problematic as the "mutable state is evil" crowd would have you believe.
-
Ohh wow! I was only trying to say that separation of concerns always seemed like the right solution for frameworks seemed to fail in DOM<->JS, though i dont think "Mutable State is Absolute Evil", but for some strange reason the solutions in those langs seem more elegant.
-
Yeah I got you.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.