!rant
Has anyone been paying attention to what Google's been up to? Seriously!

1) Fuchsia. An entire OS built from the ground up to replace Linux and run on thin microcontrollers that Linux would bog down — has GNU compilers & Dart support baked in.

2) Flutter. It's like React Native but with Dart and more components available. Super Alpha, but there's "Flutter Gallery" to see examples.

3) Escher. A GPU-renderer that coincidentally focuses on features that Material UI needs, used with Fuchsia. I can't find screenshots anywhere; unfortunately I tore down my Fuchsia box before trying this out. Be sure to tag me in a screenshot if you get this working!

4) Progressive Web Apps (aka Progress Web APKs). Chrome has an experimental feature to turn Web Apps into hybrid native apps. There's a whole set of documentation for converting and creating apps.

And enough about Google, Microsoft actually had a really cool announcement as well! (hush hush, it's really exciting for once, trust me)...
Qualcomm and Microsoft teamed up to run the full desktop version of Windows 10 on a Snapdragon 820. They go so far as to show off the latest version of x86 dekstop Photoshop with no modifications running with excellent performance. They've announced full support for the upcoming Snapdragon 835, which will be a beast compared to the 820! This is all done by virtualization and interop libraries/runtimes, similar to how Wine runs Windows apps on Linux (but much better compatibility and more runtime complete).

Lastly, (go easy guys, I know how much some of you love Apple) I keep hearing of Apple's top talent going to Tesla. I'm really looking forward to the Tesla Roof and Model 3. It's about time someone pushed for cheap lithium cells for the home (typical AGM just doesn't last) and made panels look attractive!

Tech is exciting, isn't it!?

I'm planning on making a band called Bar Fighters and will play songs like Integer Or Long, The Renderer, Test of U nit, Learn to Try ( catch )

Email html/css makes me hurt in my heart place

I HAVE BEEN TRYING TO GET A MATHS PART OF MY RENDERER WORKING FOR TWO DAYS NOW AND IT HAS BEEN WORKING THE WHOLE TIME BUT I WAS USING THE WRONG VALUES TO TEST IT THIS ALWAYS HAPPENS TO ME I WANT TO DIE

> IHateForALiving: I have added markdown on the client! Now the sys admin can use markdown and it's going to be rendered as HTML
> Team leader: ok, I've seen you also included some pics of the tests you made. It's nice, there's no XSS vulnerabilities, now I want you to make sure you didn't introduce any SQL injection too. Post the results of the tests in the tickets, for everybody to see.

I've been trying to extract from him for 15 minutes how sending a text through a markdown renderer on the client is supposed to create a SQL injection on the server, I've been trying to extract from him how showing all of this to the world would improve our reputation.
I miserably failed, I don't know how the fuck am I supposed to test this thing and if I a colleague wasted time to make sure some client-side rendering didn't create a SQL injection I'd make sure to point and laugh at them every time they open their mouth.

IE is dead ?!

NOT SO FAST.

The whole singin in Visual 2022 uses... Internet explorer renderer and... doesn't work on a Windows Server 2022 because of... "Enchanced internet explorer security policy".

I'm dying inside.

!Rant

Designer decide to have a meeting with stakeholders about UX/UI workflow for control panel of our new embedded system (no framework, no library, gui is bit per bit rendered on frame buffer).
A week later, still nothing on my table, not a mail, not a call. Meanwhile I wrote a framework, the control system, renderer, and messaging queues between tasks.
Wrote some widgets, a layout system and a view swtching mechanism, and a separate stack control to use a "back" button.

Now I am stuck for I do not know what should happen when clicking on various (non obvious) items on the touchscreen.
Fine, I'll ask the designer.

"Oh, I will write the workflow next week" (ETA time, 2 weeks. Seriously? You take a week to draw on Adobe Illustrator 20 screenshot with text and I have another week to write it from scratch in C?)
Ok, while you write it, just tell me what should happen when I click an active item.
"Well, we didn't talk about that. We just decided the colour of the icons on the screen..."
For fuck sake...

About a year ago we created as an experiment a custom AST-tree with a renderer in React. We finished this part, but never actually finished any view in our app with this, due to other timeconstraints.

This week, our new project manager looked through the usage of the implementation and basically figured it was shit. This part is fine, it was just an experiment.

But then he said that we sgould never use any AST’s ever in our project. I tried to explain that ASTs are a general concept and mentioned that for instance TypeScript uses it. Then he went bat-shit crazy and disallowed the use of typescript. We spent the next two hours explaining that we cannot avoid ASTs and that they are not bad in general.

But we are not allowed to ever implement some similar to an AST. Sometimes, I’m just blown away by the stubbornness combined with ignorance of some people. Either is fine, but not both.

Protip: always account for endianness when using a library that does hardware access, like SDL or OpenGL :/

I spent an hour trying to figure out why the fucking renderer was rendering everything in shades of pink instead of white -_-

(It actually looked kinda pretty, though...)

I'd used the pixel format corresponding to the wrong endianness, so the GPU was getting data in the wrong order.

(For those interested: use SDL_PIXELFORMAT_RGBA32 as the pixel type, not the more "obvious" SDL_PIXELFORMAT_RGBA8888 when making a custom streaming SDL_Texture)

I'm making a renderer but I can't work on it right now so I'm reading about different algorithms and stuff and I'm so hyped to carry on with it tomorrow - such a fun project!

Discovered pro tip of my life :
Never trust your code

Achievements unlocked :
Successfully running C++ GPU accelerated offscreen rendering engine with texture loading code having faulty validation bug over a year on production for more than 1.5M daily Android active users without any issues.

History : Recently I was writing a new rendering engineering that uses our GPU pipeline engine.. and our prototype android app benchmark test always fails with black rendering frame detection assertion.

Practice:
Spend more than a month to debug a GPU pipeline system based on directed acyclic graph based rendering algorithm.

New abilities added :
Able to debug OpenGL ES code on Android using print statement placed in source code using binary search.

But why?
I was aware of the issue over a month and just ignored it thinking it's a driver bug in my android device.. but when the api was used by one of Android dev, he reported the same issue. In the same day at night 2:59AM ....

Satan came to me and told me that " ok listen man, here is what I am gonna do with you today, your new code will be going production in a week, and the renderer will give you just one black frame after random time, and after today 3AM, your code will not show GL Errors if you debug or trace. Buhahahaha ahhaha haahha..... Puffff"

And he was gone..
Thanks satan for not killing me.. I will not trust stable production code anymore enevn though every line is documented and peer reviewed.

Never thought I'd say this but...I wish IE6 was back for Outlook.

//After Outlook 2003, Microsoft decided that MS Word was a better renderer for emails than IE6 was, what the hell Microsoft?! Get it together man.

For anyone who's gone through setting up a Vulkan based renderer from absolute scratch.

Writing an efficient, modern renderer is truly an exercise of patience. You have a good idea? Hah, fuck you, GPUs don't support that. Okay but what if I try to use this advanced feature? Eh, probably not going to support exactly what you would like to do. Okay fuck it I'm gonna use the most obscure features possible. Congratulations, it doesn't work even on the niche hardware that supports that extension

If I sound jaded, ya better believe I f*cking am! I cannot wait for more graphics cards to support features like mesh shaders so we can finally compute shader all the things and do things the way we want to god dammit

Been working on a rust game framework that im really proud of, but the part I’m most proud of is the renderer, 3D graphics from scratch is really fun

Hey everyone!

TL;DR I'm looking for a way to make a webapp for iOS.

I am developing an app for iOS devices. I am more familiar with JS, CSS and HTML, not to mention I have already created a fair chunk of the app. So it would be great if there was a solution that worked like UIWebView/WKWebView. I've had numerous issues with both of these widgets. UIWebView worked the best, most like a normal browser renderer, however still has some very annoying anomalies. For instance the input box could be covered up such so that you could still type but not see what you were typing, no other web browser does this. I've had plenty of issues that I have had to find hacky workarounds for. Is there a better way? I've heard of Titanium by Appcelerator, however I wanted to get as many opinions as a can.

Thanks!

Fuck Outlook for desktop in particular.

Why would they still be using their crappy word-as-renderer in this day and age? Why are they ignoring perfectly sensible CSS from elements that aren't tables? Make it make sense!

It's especially galling that they've resolved it in the web version and in the native apps, _except_ desktop for windows. Even Mac is fine!

Holy fucking shit are email clients bullshit.
I don't know what happened there but if you thought the chrome-firefox-ie-egde gaps back in the days were sick - let me tell you.. email clients are made by the devil himself. All of them. All of them? Yup. Because he made some of them being owned by apple, working beatuiful and no weird stuff.
But on the same end he made some of them owned by microsoft and their office Studios. They use the word engine to render html emails. Read this again. Read it without starting to cry in agony.
But thats not enough. Let's make some of them use an ie-engine and the mac os variants going to use some webkit based renderer. This way there will be no valid ruleset to make it look good on all of them, isn't this great??
Now this might be hell already. But lets pour more salt into these wide opened wounds.
Let there be Germany and United Internet, owning trash like Web.de and GMX, whose android clients going to work completely different across Android and app-versions!
Once you've mastered these, let me introduce you to gmail. Lets take only the body node of your email and do some fuck up with it, so you have to display a non-responsive variant on mobile.
Now you might be thinking "but there are web-based clients, they'll do good ain't they?" Long story short: fuck you.
Not enough.
Let's go back to ms.
Hey dude lets make it possible to scale up your whole system. So old people can read shit better. And now the funny part: let's make it so that the word rendering engine, rendering emails goes completely mayhem on your mail, so it looks like a completely different thing! (:

If you ever receive a newsletter in your inbox and that shit looks like it's planned to look like.. appreciate that shit. Sacrifice a virgin as thanksgiving for it.

TL;DR:
E-Mail needs to die. I'm doing this for over 2 years now and this shit needs to stop asap.

Fun times with postscript:

I have two EPS files that are generated by a program.
In there there is the postscript describing the file (~6000 lines) and then the preview image as TIFF. Each ps and TIFF image on its own renders correctly and looks good.
Now the fun part: The ps in combination with one of the images works, with the other image it doesn't. Somehow the ps-renderer tries to interpret the TIFF-data, which yields nonsense and the renderer stops altogether. But only for one file not for the other. And it's definitely not the ps, because if I switch the preview images the other file doesn't work.

People are like a stable set of database artifacts blah blah
Repeat this repost that

Did anyone ever figure out why it is that trained human detection models don’t work better ?

All you’d think they’d have to do is run an animation renderer to create data representing a human figure in every conceivable position imaginable with limbs moving into positions that were within certain tolerances in different positions with different textures

I don’t personally think the full capability is being represented

So currently working on a basic game engine written in Vala using SDL, fuck me it is such a rabbit hole!

Have a basic renderer and and was using the default SDL frame rate manager and decided to write my own so I could knock out using the SDL gfx package.

So now I have to create a window manager and renderer manager just to handle a basic framerate manager that isn't completely negated by VSYNC....

What's a duck's favorite web equation renderer?

MathQuax.

Salt is awesome, no questions about that. YAML is giving me headaches, but it's my fault and eventually I'll get used to it. But this being my first encounter with jinja, WHO THE HELL THOUGHT THIS PIECE OF CRAP DESERVES TO LIVE! Instead of writing python inside {% %} you have to write kinda pseudo python and I just spend over hour trying to build list inside for. Yes, great idea, scoping fors, and lets make it hard to escape scoping, beacause it would be a shame if somebody COULD ACTUALLY DO SOMETHING USEFULL. I though several times of using different renderer, but I want to keep my code readable and mainrainable and in the end I found a workaround, but still, Jinja, YOU SUCK!

Multiplayer 3D engine architects:

While building the inital engine of your team's renderer and network systems, what were the most helpful things members of your team could provide?

What's the worst part about testing React components? Using the equivalent of fucking stone tools to do your component integration tests! We got errors with no context and errors with no stack trace, just spewing out bullshit! A sample:

The classic "Can't access .root on unmounted test renderer"

The unforgettable and ALWAYS visible "Warning: An update to YourShittyComponent inside a test was not wrapped in act(...)."

We do love it!