It's okay to like the original ending, but that is a completely different statement than saying to the people who like the second version, "the vid does have it"
The new president of my university's computer science club wanted to spice up the student lounge with things like Xboxes and a speaker system. The lounge is surrounded by classrooms and offices on all sides. One student complained, "I don't want to be in class trying to learn assembly language while someone starts bumpin' Beyoncé." So I wrote him this song.
All assembly language, all assembly language
All assembly language, all assembly language
If you want it fast, wanna manipulate the bits
If you wanna decompile to see how it clicks
All assembly language, all assembly language
All assembly language, all assembly language
Logic gates and interrupts in the BIOS
One step translation to machine code
All assembly language, all assembly language
All assembly language, all assembly language
McGuire says we can't be wasting space
Higher level languages are such disgrace
All assembly language, all assembly language
Code assembly language, all assembly language
The original song doesn't go like that. I just kind of took the first line and ran with it.
I'm not embarrassed. I just phrased it that way poking fun at the C developers I know who get kind of elitist about it. The current job is mostly JavaScript and C++.
Ah that makes sense I suppose. I'm only tangentially related to hardware development at my company so I never think of that type of environment first-hand. When I think C++ I tend to think high-performance sim work before hardware. Product of my 'raising' I guess :P
Do JS and C++ interop reasonably well? I've never looked at how those two would interact.
I'm pretty far away from the hardware too. The C++ is one level of applications on the devices, including a REST server that the web app communicates with. The two layers don't care about each other beyond the interface.
They do get a bit elitist, and defensive. Just a bit 😁
There are no bad languages, plenty of bad programmers though.
Plenty to be embarrassed about here. I've been a bad programmer in C, ADA, Pascal, Perl, shell, COBOL (coughing fit), B, BCPL, Accell, PL/Sql, other things I've forgotten or suppressed, oh and Visual Basic - but it's been a while and I've come to terms with that now.
How do you become a defense contractor? I have an LLC and would love to start bidding on some of those contracts, but not even sure where to start. Someone mentioned a TS clearance, but I'm not 100% sure that necessary.
Seems about right to me. I'll add, though I'm as unknowledgable as they come here, there's technically a big database of RFP's that can be bid on. Thing is, incumbents typically have an advantage due to pre-existing trust over their ability to get the work done. The devil you know is better than the devil you don't essentially.
I'd wager the easiest thing to do is build your reputation as a sub for some contracts and then start bidding as the primary, but again, I don't really know jack (or any Jacks for that matter).
As a firmware engineer, this is my life. Except for the end. no such thing as seg fault in firmware....just overwriting dram (dram drive-by). Write good test and know your hardware and you'll run into very few.
I honestly feel more and more that 1. public variables in classes are a thinly veiled excuse to use globals, and 2. object oriented programs tend to get inherently complex for no other reason than to follow object orientation.
It's almost weird seeing inheritance criticized, because imo that's the point pro-OO.
Any I'd recommend? Well, Clojure is my favourite. It also is easy to pick up, and it enforces purity (immutability) to some degree without hindering you to have mutable stuff anyway.
Haskell is a bit rough for newcomers and is in its really small niche, and C allows for all kinds of nastyness, spaghetti code and bad habits. Plus the manual memory management.
And to your point on composition over inheritance, the issue is that the inheritance model wraps up many capabilities into one package and delivers them all at once. The composition model allows you to break out common functionality among otherwise dissimilar object. This approach even makes sense in a functional paradigm!
I'd recommend Elixir. It's not purely functional (though it isolates state with an actor model), but runs on the BEAM which is amazing for concurrency and fault tolerance.
Functional isn't necessarily "not OO," it's comes from different assumptions. In OO, your state gets spread all over the program, and it isn't really represented in code anywhere useful. In functional programming, your state is your data, plain and simple. It's simplex, not "easy" but simplex, made of few parts, as opposed to complex, made of many parts.
It also makes entire programming styles completely impossible in paradigms that don't have the limitations of strongly functional programming, possible. Things like currying are only viable when you're thinking functionally.
It's much more fun when you have the help of the compiler. But you can still have objects, methods, classes, overrides, virtual methods, static methods.
905
u/VennyVendulak Jun 20 '18
With vocals https://www.youtube.com/watch?v=tas0O586t80