Search
481 results for “develwithoutacause”
-
CW: #Sandman S1 light spoilers
#Sandman The fight with Lucifer has some real #Calvinball energy to it.
"I'm a planet so you can't hurt me."
"Oh yeah, well I'm a nova that destroys planets!"
"Oh yeah, well I'm a universe!"
"Oh yeah, well I'm anti-life, that beats everything!"
Sit down Lucifer, you're making all this up.
Why didn't Dream just say he's anti-anti-life? Is he stupid?
-
#TIL about #MicroData, a way of embedding metadata inside #web pages for #SEO.
https://developer.mozilla.org/en-US/docs/Web/HTML/Microdata
Does anyone actually do this in 2024? I feel like semantic HTML combined with #OpenGraph mostly solves this problem. Is this a useful tool for web developers?
-
Note to self: #esbuild playground environment with all the settings for debugging `ngDevMode` tree shaking:
(I find the configuration very confusing to figure out and keep struggling each time I need to do this.)
-
Since it's related, here's the `removeEventListener` API I wish we had:
```javascript
const removeListener = window.addEventListener('something', () => { /* ... */ });await someTime();
removeListener();
```Benefits:
1. You only provide the handler once, so it works great with lambdas. You don't need to keep a reference to the handler just to remove it later.
2. You don't need to provide the event twice. It's additional information to hard-code and/or dynamically track.
3. You can't accidentally `removeEventListener` on a function which was not bound in the first place (which is a no-op that often indicates a bug such as `removeEventListener('something', foo.bind(this)`).This design is basically a copy of the way #RxJS handles subscriptions, but I find this much more ergonomic and intuitive.
-
Over the last few days while working on an upcoming blog post I've performed quite the yak shaving:
1. I wanted to use `@layer` in a #CSS demo (ironically one showing that it doesn't solve this particular use case).
2. My auto #CSP setup using #JSDom and #CleanCSS failed to parse `@layer`.
3. I upgraded #CleanCSS.
4. I removed #JSDom and replaced it with #parse5, which works with `@layer`.
5. I wanted to use `Object.groupBy` here which requires `target: "ES2024"` in #TypeScript.
6. Therefore I needed to upgrade TS.
7. Upgrading TS broke #Karma for reasons I couldn't understand.
8. Therefore I migrated from Karma to #Vitest (which I've wanted to do anyways).
9. Now #Netlify is confused that I have both an 11ty and Vite project and fails, asking me to pick one.
10. I pick one in `netlify.toml`, but a bug in Netlify refuses to accept it. -
I feel like it's one of the few things you could do with the franchise without #Kojima, since you're just copying his work.
Only real requirement to me is that you need #DavidHayter, but I think #MGSDelta made that happen, so maybe it's actually possible.
-
Question for people using #MicroFrontends and #Monorepos: What do your #integration tests look like?
The #Google model of monorepos always builds everything at HEAD, but doing so would not catch version skew issues that come with independent deployments. That implies that your integration tests _cannot_ just build and run everything at HEAD, you actually have to deploy each change individually to a staging environment and alert on failures.
That feels like a much more complex setup than I'm used to seeing for integration tests. Do people actually do this or is version skew a giant blind spot for microfrontend testing?
-
@jaredwhite Yeah I am wondering if it would make more sense to have a separate community protocol for initialization.
I'm very strongly of the opinion that you should never be able to get a reference to an uninitialized object (I think this is sometimes called #RAII?) Unfortunately that ship sailed for web components a long time ago. Constructors are worthless in this context too (and terrible per https://blog.dwac.dev/posts/ctor/). So maybe a protocol around initialization would help, whether that is or isn't `defer-hydration`.
-
#TIL #JavaScript #OptionalChaining "short circuits" the rest of the evaluation so you can safely write `a?.b.c()` (no need for `a?.b?.c()`).
Personally I find it kind of confusing that introducing parens or a variable changes behavior, but I can see the reasoning behind it.
-
More seriously, this is a legitimate #cybersecurity vulnerability in #USBank which should be fixed ASAP.
USBank is training it's users to just put their banking information into any site which asks and actively hurts the security of it's own users as well trains those users to do the same for any other service. What's the point of telling users to look for the padlock and check the origin, if sites will disregard it altogether anyways?
-
Took down the last boss! Only on the third attempt, but he's definitely a tier harder than the rest. I'm not sure I like how mobile he is, as #Executor I spend 80% of the fight chasing him down.
#RiversOfBlood really carried the fight though, gave me some range I don't normally have.
Having completed the main content, I have enjoyed #Nightreign and feel it's an interesting twist on the Souls formula. Racing around the map for upgrades and levels while working together as a team is very fun and often builds to a tense ending.
The various characters are awesome and I love Executor in particular.
-
Are there any web frameworks out there which push the majority of user code off the main thread?
I'm thinking of an architecture such as automatically loading your #React components into a #WebWorker, doing all rendering off main thread, and then having the framework pass the VDom back to the main thread to be reconciled on the actual document.
I know various frameworks have experimented with web workers (including #Angular), but I don't know if any quite used this kind of approach? I'm curious if anyone has tried this and what the outcome was.
-
I'm part way through the #Ahsoka series and I have to say, it was a really weird narrative choice to have #Dory show up and ask the star whales for help. Way too convenient that Earth whales and star whales speak the same language.
I guess this is just the #DisneyExtendedUniverse we live in now.
-
I had been hoping to spend some time this weekend on #HydroActive, but #Akuma is just too much fun right now.
-
RE: https://hostux.social/@defcon201/116324484796527679
Quick #story time: I was on a team which accidentally shipped sourcemaps to production!
The production server would serve sourcemaps for local dev, and we built sourcemaps in prod to deobfuscate errors but they weren't provided to the server in the prod environment.
You might see the hazard there. An innocuous change to our #Bazel build structure accidentally pulled in sourcemaps into the server, which it then helpfully served.
This was an app in the #Google monorepo too, so we were revealing all our source code as well as all our dependencies!
-
CW: #EldenRing #ShadowOfTheErdtree #Midra
Just beat #Midra and I think he's my favorite boss of the DLC so far. His attacks and combos are really clear, so none of his moves felt cheap.
The #FrenziedFlame stuff is really cool set dressing in the area and fun attacks. He looks awesome with the yellow fire effect and I'm glad they don't really do damage over time. It would have been really easy to treat his lingering fire like #Mohg's bloodflame and get annoying very quickly, but the devs didn't go that route and I'm greatly appreciative.
My one nitpick is that the boss can occasionally one-shot you if an attack also triggers madness, since you're stunned and likely to get hit a second time plus the raw madness damage. A 1-2-3 hit like that will usually kill. It's not too difficult to manage the madness meter or use some consumables, so I don't mind it too much though.
10/10 boss, would go mad again.
-
Am I the only one who thinks we got #greenfield and #brownfield backwards?
I always hear those terms as planting a farm, where a brown field implies you can do what you want from scratch, but a green field means you have to work around the existing vegetation and produce.
Apparently the terms come from civil engineering, not farming and refer more to developed / undeveloped real estate.
en.wikipedia.org/wiki/Greenfi...
en.wikipedia.org/wiki/Brownfi...Would most people intuit that meaning without this background? Feels like a bad analogy for software engineers.
-
Playing with #ESModules in #Node today and had some fun.
-
What could we do if the #web spec supported defining multiple #ESModules in the same file? I wonder if that would allow runtime linking of chunked #JavaScript in more flexible ways than the format can currently support? I'm imagining a syntax like:
```
// File: /user.js// No need to request /logger.js, just
// inline it the first time it's needed.
module '/logger.js' {
export function log() { }
}// Define `/user.js` module.
import { log } from '/logger.js';
function logUser() { }
``````
// File: /analytics.js// Can reuse '/logger.js' without having
// to download it separately.
import { log } from '/logger.js';
function collect() { }
```This way servers could trivially move '/logger.js' between '/user.js' or '/analytics.js' at runtime per-user based on whatever chunk the user downloaded first.
https://github.com/tc39/proposal-module-declarations seems to explore this, though everything is lexically bound so I don't see how you could support this particular use case. Maybe I'm missing something?
-
Literal #ShowerThought #idea: A #JavaScript "composite" #WeakMap. Returns a value for a given array of references. All weakly referenced to avoid memory leaks. Something like:
```
const map = new CompositeWeakMap();
const keys = [ {}, {}, {} ];map.set(keys, 'test');
map.get(keys); // 'test'
```Not 100% sure it's possible since `WeakMap` is only keyed by a single reference, but I think it's possible if you chain two `WeakMap` objects together. I have an implementation in my head, but I'll have to actually try it to see if it works for real. 🤔
-
Whoo! Took down Consort (actually hitless!) and wrapped my RL1 All Remembrances run.
Had a lot of fun with this and I'm glad I did it, but I think now it's time to play something I haven't beaten multiple times already.
-
-
Interested in #Microfrontends? I'll be chatting with @manfredsteyer.bsky.social tomorrow about how we're tackling them at #Google and #Angular. We hope you'll stop by!
https://www.meetup.com/angular-meetup-graz/events/312845056/
-
Just published a #blog post on #CSS inheritance and how to isolate multiple #microfrontend web applications running on the same page.
There's some fun nuances with `initial` and `revert` as well as background on user-agent stylesheets. Hope you enjoy!
-
Just published a #blog post on #CSS inheritance and how to isolate multiple #microfrontend web applications running on the same page.
There's some fun nuances with `initial` and `revert` as well as background on user-agent stylesheets. Hope you enjoy!
