Notices by Ya favorite tho(ugh)t (are0h@playvicious.social), page 65

@kyzh Well, we're kind of all here to play a role and contribute to making this place better, and that's just one of mine.

My alleged 'profile' makes me a bit of a target because a lot of folks don't like it that a non-white guy is outspoken about these things, but I don't mind because long term we're all going to be the better for it as well as learning to push back on these bigots.

And big thanks for the support. It all really helps to keep it going.

@rootfs_ext2_gz That's pretty close. They have Indexeddbs, which is nice, but it's incomplete with cache storage.

Yeah, it really is. It's becoming the new I.E.

@somarasu Then fuck Apple. If they can't get their shit together, we'll just use something else.

Anybody can get it.

Back to Firefox Developer Edition as my dev browser because that's just stupid.

I might just make FDE my main because enabling service workers but not the storage cache is a straight asshole move by Apple.

Let me go make some food and calm down.

@somarasu I'm really kind of ticked off right now man.

It's absolutely absurd that they'd support service workers, but not the cache they use to store offline data.

That doesn't make a lick of sense...

@rootfs_ext2_gz It's really frustrating. I've spent the better part of a day implementing an elegant caching solution and I'm thinking I'm just doing something wrong, but they just don't support cache storing.

Which is kind of insane considering it does support service workers. If they can't store data, what the fuck is the point??

So cache storage works on iOS Safari, but not desktop?

What??

@kaniini Agreed. That's a good way of putting it.

@kaniini Yeah and I see the value of it because it's really slick if that's the kind of app one is building.

However, it does lock one into building that kind of app going forward and for my project, I want to avoid being locked into any particular way of building.

The stuff that I would be using in Vue is stuff that I can build myself, although it won't be as sexy.

But it won't require an additional step to implement either, so I find that preferable.

I think I'm gonna pass on implementing Vue into Fipamo.

While I definitely understand why people dig it because modularizes ui creation in a purposeful way, I also think it adds a layer of complexity to my project that I'd rather avoid. And I'm trying to keep Fipamo as framework free as I can.

Of course this means I'll have to figure out some new methodology as I switch to a cache first application, but I don't mind putting that work in upfront to keep everything thing as lean as possible.

It's a beautiful new day, lovely people.

There are so many possibilities and directions you can go today. Embrace them. Enjoy them. Revel in them. You've earned every single one of them to get to this point.

That's pretty cool..

On one hand, my old school programming sensibilities are screaming at me about having scripting, css, and html all in one file.

On the other the organization of Vue components is very attractive because it allows me to think in terms of tasks for that particular element. And I can still use es6 and stylus.

It's a different way of building, but it kind fits if I'm going to be working cache first.

I had the most filthy and lovely dream last night.

I'm trying to figure out how to put it into words. It was really weird, but kind of wonderful.

Ok I did a little bit of code work. Now I can chill.