uasm

> "had a couple of jobs at uni as an iOS dev"

That's a great start, but what kind of jobs are we talking about here? I'm asking because you might want to invest into building more experience before breaking off on your own. I'm talking about possibly larger projects, cooperating with other teams, driving products forward, working with PMs/customer requirements and so on. One way to get there is to work at a larger organization. People place value on experience.

> "Problem is, as a student I am trying to go freelance and start getting clients by doing small projects."

Is this more-or-less your first job straight out of school?

Cash free societies?

> "ELI5 please. why should I care about this."

Sounds like exactly the tool for your kind! ;)

The true solution though, would be for people to wake up and realize that in most cases, those so-called "ivy-league" colleges set you up for nothing you couldn't have gotten elsewhere. That you're NOT in-fact better off at 22 with a 150,000$ debt, which you could've avoided by attending a different institute. That the quality of education in "less prestigeous" universities doesn't necessarily "fall" from that of Harvard's.

Edit: Addressing the comments about how it's all about joining that Alumni circle.

I've attended an ivy-league alumni dinner party recently (graduates from multiple "high profile", internationally acknowledged institutes). Save for several senior people with interesting stories, most others were working on their "next Lyft"/"next Airbnb"/"Facebook for %s"/"%s but with AI!" startups. Everybody had a suit and a nice lapel pin to show for it though. Some even wore a bow-tie, no less!

At some point it stops being a club of outstanding members of society, and instead, it becomes a "I took a huge loan to buy my way into this" club. Make of it what you will.

Lesson learned: avoid ccTLDs. Reduce future risk by opting in for .com/.net/.org instead.

Imagine the thousands of people using X@Y.eu as a personal email address. Those domains will be made available for purchase soon thereafter:

> "Twelve months after the UK withdrawal, i.e. on 30 March 2020 00:00:00 CET, all the affected domain names will be REVOKED, and will become AVAILABLE for general registration. For security and stability reasons, the release of all affected domain names will occur in batches from the time they become available."

> https://hacker-tools.github.io/lectures/

Literally none of these have anything to do with proper information security/hacking/penetration testing. Will you please consider to stop abusing the term "hacker"?

> "The idea would be to give people a leg to stand on so they can take risks, not hide in their confort zone..."

560€ per month, in Finland, is not enough take people out of their "comfort zone". Check out the rental prices in some of the larger cities: https://www.vuokraovi.com

> "If losing $25k is life changing, you should pay some money to reduce the risk."

What about the risk of your insurance company going bankrupt? Or the risk of your insurance company fighting tooth and nail to avoid paying you?

> "Yes. You can go into settings and remove it easily though."

Hopefully, will be the next mechanism to be phased out via legislation.

> "Let me rephrase that. Is x86/x64 (or ARM, for that matter) architecture ideal to compile WASM into? Or could a different architecture be designed that would result in better performance?"

I'm sure you could compile WASM into Japanese or French if you had to. Maybe then, our French-native CPUs would finally be able to process "sudo fais moi un sandwich". My point being, you're asking a very broad, very theoretical question.

Are CPUs these days not performing well enough for most applications? If so, is it necessarily due to the complex instruction sets powering those platforms?

> "I wonder if wasm is feasible to target in hardware. I mean, there were hardware Java bytecode implementations, and that's a lot higher level, so it's definitely possible - but is it worthwhile? Are there any idiosyncrasies in wasm that make it slower than x86 or ARM, that could be fixed if the underlying architecture was more accommodating?"

You're asking for unified, standardized, cross-vendor hardware + instruction sets.

Why not do this other way around though? "Compile" JS to WASM, then to x86/x64. Finally just execute on the bare metal.

> "can you elaborate on why that is?"

Might as-well suggest we use a single letter, instead of 26.

> "When the strike passes the edge of the circle, it's no longer a zero, it's a Danish or Norwegian "Ö" (Ø). It's been a part of their alphabet for centuries."

You can't please all the people, all of the time. There are ~21 million people living in Scandinavia - and for them, that could indeed be somewhat of an issue. What about the rest of the planet?

> "By badly thought out design and a need to be different for no reason, you just returned to square one, because the font is now unreadable for anyone that knows or works with the letter Ø."

Out of curiosity, what would you consider to be a better design?

> "Life gets in the way of scheduled work (on-call)."

Scheduling 24h work days will inevitably cause "life to get in the way of work". On-calls commonly take a week or two at a time. Stop de-legitimizing work-life seperation.

> "A guide to being on-call... we all have lives which might get in the way of on-call time"

How dare those engineers live a life. They're on-call goddammit.

> "Useful commentary from /u/hash_define on /r/ReverseEngineering:"

I would say that a lot of the GH/IDA differences probably come down to UI and usability. Most of the tooling in the RE world today is lacking in those spaces. The software simply isn't "comfortable" or intuitive enough to work with. Be it IDA/olly/windbg/radare, they're all desperately lacking a proper, solid UI. The good news is, most of them support a plugin/extension architecture - so in theory, most of the features GH provides could've ended up as an IDA plugin - so that the researchers receive the best of both worlds.