Do you have a couple accessibility experiences from engines you thought were good? Maybe not "compare" to avoid flame wars, but maybe some highlights.
196 karma · joined May 8, 2012
If one is required to be concerned with not "being an asshole", how are risky ventures ever undertaken?
edit: root comment here is mentioning NULL checks and actually being helpful
Indeed it is not free content, the volunteers that edited the UE4 wiki must be pretty disappointed. But Epic isn't broke and the vague reasoning they offer is insufficient to me and many others.
p.s. Coincidentally I am a daily user of AwesomeWM. Thanks for your efforts!
Not that this is a good thing. It's childish to be surprised and indignant about these companies' policies and behavior like they're your buddy or something.
Conferences are nearly all in-person live ads, cloud ads disguised as talks, or tutorial talks so shallow a Googling is better.
Triple that for infosec industry.
If owing thousands as a US peasant earns you harassment and dozens of calls a week, I'd love to see the Experian leadership get thousands a second if we're staying proportional.
Corporations are people and all.
When I'm hot on a new video game, I can't wait to fill the most immediate next hours on doing it. What was that for you at some point? I enjoyed QBasic in gradeschool and revisiting after years in the field was really fun.
Whatever that code is, I suggest pursuing it even if it's not
a) something everybody on here says we need to be doing
b) related to your dayjob
c) related to that "big project" that you need to do perfectly
I wish you the best.
P.S. strike perfectionism out of your mind
P.P.S: Practically look into using the Pomodoro Method
P.P.P.S: Either start or stop doing drugs. Or see a board-certified medical professional if you think that would be dope. It is.
edit: formatting as always
12 years in industry across stacks b2b dev experience here. The word "accessibility" or "disability" never even uttered out loud by developers, stakeholders or otherwise during every single project.
Maybe in like 50 more years it will be more common?
It's not just deadlines that gets a11y chopped off. It's not even remotely considered to begin with, unless a client demanded it specifically. Which never happened. Closest thing I've seen is internationalisation demands.
I've read sentiments and articles indicating that if you DO include good a11y support - these users love you. It garners massive loyalty, as one could imagine.
If you're a grunt serving in the lines? Good luck filling out a comment card after your desk-eaten 23 minute brown bag lunch and maybe the CEO won't fire you for the insubordination of suggesting work off of the most minimal track to $$$. I actually get anxiety sitting here thinking of how much trouble and internal political strife that would have caused in some places.
Businesses in the software industry care 0%. Negative zero.
Good job! Gonna use.
I have a PWA that will clear all that up for you, friend.
In the nasty real world, these build systems introduce more issues for more people. Then linking the shared object or DLL adds management issues, naming issues, arch etc. But that's for separate dependency building as a binary.
Has every one of these side compilation steps gone perfectly for you? No. At some point they wasted your time.
This concatenation-build step is done reliably beforehand, even if simple, can be assembled and be tested by the releasing party. Saves the user some trouble.
A pre-built binary is about as easy if done sensibly. Boost is mainly header only but has some libs still requiring linking, which requires you digging into that library's particulars.
All of those are steps that have tradeoffs in time, attention, flexibility and risk.
Careful of that word "... just". Just do this! I can just do that! The full hassle/cost requires pulling out of just the compile step, in this instance.