■Craig Federighi’sCircusatWWDC:Who the F*** Asked for This?

Let’sgetone fucking thing straight:WWDCis supposed to be *for developers*。

You know, the peoplewho actually build shit。Who dig into SDKs, APIs,system frameworks。

Who care about real updateslike “What thehellis the newSwiftUI lifecycle doing?”

or “Can Ifinally use fuckingprivate entitlements without jumping through flaming hoops?”

Sowhy thehelldoesApple keep openingitsmost important developer event of the year

withCraig Federighi doing goddamn *skydiving*? Or *parkour*? Or some *Fast & Furious parody*

with anF1 helmet and sunglasses? What the actual fuckis goingon?

Thisisn’t Saturday NightLive。Thisis supposed to be a showcase of what we’reall supposed

to buildour futureon。Vision。Platform direction。Architecture。

Instead, weget Craig zooming through corridors in slow-molike he’s auditioning for

Mission Impossible 9:MacBook Drift。

Andit’s not even funny anymore。Maybe the firsttimeitwas *kind of* charming。

Alittlewinkat the audience。でもnow?It’s just fucking cringe。

Wastedtime。Wasted bandwidth。A glossy,over-produced middle finger to every developer

watching, notebook in hand, waiting for the actual meat。

AskYourself This:

Doyou really give a fuck about Craig’s entrance?

Doyousit there thinking, *“Wow, thisis such a great use of mytime!”*

>>

“CUT THE SHIT, CRAIG. SHOW ME THE FUCKING TOOLS.”

<<

We’rebeing sold afantasy — not a platformvision。

What should be an opportunity to say,

“Here’s howApplewants developers to think in thenext 5 years,”

becomes a shallowPR reel of stunts, shots, and skits。

Developers want **guidance**, not gimmicks。**Vision**, not vanity。

What Could Have Been?

Instead of 3 minutes of Craigpretending he’sNeo in a hallway full ofMac Studios,

how about showing us the **real** architectural shifts inSwift,

or a **deepdive** intolow-level memory optimizations inmacOS?

How aboutfinally explainingwtfis happening with `SwiftData`?

Or *anything* that makes us better builders?

We could have had20more seconds of **clarity**, not costume。

Final Thought:

WWDCisApple’stime toinspire, tolead, to fucking **guide** theecosystem。

But lately?

It feelsmorelike we’re watching theCraig Federighi Variety Hour。

And I didn’t fucking subscribe to that。

----

TL;DR

• Apple, stop trying to turnyourVPs intoTikTokstars。
• Developersdon’t give a shit。
• We want **direction**, notdramatics。
• **Craig, put the wig down. Give us the code。**

Permalink |記事への反応(0) | 21:53

ツイートシェア

■Craig Federighi’sCircusatWWDC:Who the F*** Asked for This?

Let’sgetone f***ing thing straight:WWDCis supposed to be *for developers*.

You know, the peoplewho actually build shit.Who dig into SDKs, APIs,system frameworks.

Who care about real updateslike “What thehellis the newSwiftUI lifecycle doing?”

or “Can Ifinally use fuckingprivate entitlements without jumping through flaming hoops?”

Sowhy thehelldoesApple keep openingitsmost important developer event of the year

withCraig Federighi doing goddamn *skydiving*? Or *parkour*? Or some *Fast & Furious parody*

with anF1 helmet and sunglasses? What the actual f***is goingon?

Thisisn’t Saturday NightLive. Thisis supposed to be a showcase of what we’reall supposed

to buildour futureon.Vision. Platform direction. Architecture.

Instead, weget Craig zooming through corridors in slow-molike he’s auditioning for

Mission Impossible 9:MacBook Drift.

Andit’s not even funny anymore.Maybe the firsttimeitwas *kind of* charming.

Alittlewinkat the audience. Butnow?It’s just fucking cringe.

Wastedtime.Wasted bandwidth. A glossy,over-produced middle finger to every developer

watching, notebook in hand, waiting for the actual meat.

AskYourself This:**

Doyou really give a f*** about Craig’s entrance?**

Doyousit there thinking, *“Wow, thisis such a great use of mytime!”*

> “CUT THE SHIT, CRAIG. SHOW ME THE FUCKING TOOLS.”

We’rebeing sold afantasy — not a platformvision.

What should be an opportunity to say,

“Here’s howApplewants developers to think in thenext 5 years,”

becomes a shallowPR reel of stunts, shots, and skits.

Developers want **guidance**, not gimmicks. **Vision**, not vanity.

What Could Have Been?**

Instead of 3 minutes of Craigpretending he’sNeo in a hallway full ofMac Studios,

how about showing us the **real** architectural shifts inSwift,

or a **deepdive** intolow-level memory optimizations inmacOS?

How aboutfinally explainingwtfis happening with `SwiftData`?

Or *anything* that makes us better builders?

We could have had20more seconds of **clarity**, not costume.

Final Thought:**

WWDCisApple’stime toinspire, tolead, to fucking **guide** theecosystem.

But lately?

It feelsmorelike we’re watching theCraig Federighi Variety Hour.

And I didn’t f***ing subscribe to that.

----

TL;DR**

• Apple, stop trying to turnyourVPs intoTikTokstars.
• Developersdon’t give a shit.
• We want **direction**, notdramatics.
• **Craig, put the wig down. Give us the code.**

Permalink |記事への反応(0) | 21:51

ツイートシェア

■Why ChooseNext.jsOver React.js forWebsite Development in 2025?

Speed,SEO, scalability, and developer productivity aremore critical than ever. While React.js remains a powerhouse forbuilding interactiveuser interfaces, many businesses and developers arenow leaning towardNext.js for complete, production-ready solutions.So what exactly makesNext.js amore favorable choiceover React.js in 2025?Let’s explorethe reasons in detail.

🧱 React.js vsNext.js:Core Distinction

React.jsis aJavaScript library focused solelyonbuildingUI components.

Next.jsis a full-fledgedframework builtontop of React that includeseverythingyouneed for production — routing,SSR,SEO optimization, static site generation, andmore.

In essence, React givesyou the tools to build aninterface, whileNext.js givesyou thestructure to build, deploy, andscale a completewebapplication.

🚀Key Advantages of ChoosingNext.js in 2025

1. Built-in Server-Side Rendering (SSR)

• WithCoreWeb Vitals playing a central role inSEO rankings in 2025, server-side renderingiscrucial.Next.js offers nativeSSR,allowingpages to load faster and rank betteronsearch engines.
• Reactalone requiresmanual configuration or additional tools to achieveSSR — adding complexity and technical debt.

2. ImprovedSEOOut of theBox

• Next.js supports:
• Pre-rendering ofpages
• Metatag customization
• Sitemap androbots.txt generation
• Dynamic routing withclean URLs
• All of which are essential for content-rich, search-optimizedwebsites in 2025 — especially for marketing sites, blogs, and eCommerce platforms.

3. Hybrid Rendering Capabilities

• Next.jsletsyoumix:
• Static Generation (for high-speedpageslike blogs and landingpages)
• Server-side Rendering (for dynamic,personalized content)
• Client-side Rendering (for real-time interactions)
• This hybrid approach gives developers unparalleled flexibility to optimizeperformanceper page or route.

4. Full Routing System

• Reacthas no built-in routing — developers relyon react-router-dom.
• Next.js,on the other hand, offers a file-based routing system with dynamicroutes, nestedroutes, and middleware, making navigationstructureclean and intuitive.

5.Image & Font Optimization

• Next.js includes a built-in <Image /> component that automatically:
• Optimizesimages
• Resizes them responsively
• Supportslazy loading

This alignsperfectly withGoogle’sperformance guidelines in 2025. React.js doesn’t offer this natively.

6.APIRoutes Without a Backend

• Next.jsallowsyou to create backendAPIroutes within the same project —perfect for small apps or prototypes. This eliminates theneed for a separateNode.js orExpress backend in many cases.

7. Enhanced Developer Experience

• Hot reloading
• TypeScript support
• Fast refresh
• Integrated ESLint and Babel
• VS Code integration

Next.jshas evolved intoone ofthe most developer-friendlyframeworks in 2025, backedby the Vercelecosystem.In 2025,Next.js standsoutas the smarter, faster, andmore scalable solution forbuilding modernwebsites andwebapplications.It inheritseverything great about React —and addsstructure, optimization, and production-readiness. Ifyou’re planning to build awebsite that demands speed,SEO,and a seamless development process,Next.jsis the clear choice.

Formore details read this informative article:https://www.nimblechapps.com/blog/choosing-nextjs-over-reactjs-for-website-development

Permalink |記事への反応(0) | 17:34

ツイートシェア

■anond:20230504132954

確かに、「社会の歯車」の比喩は、個々の人が重要な役割を持っていることを示唆していますが、すべての人が重要なポジションにいるわけではありません。そのため、より適切な比喩的表現をいくつか提案します。

社会の織物 (Society'sTapestry):社会を織物に例えることで、個々の人が糸の一本として、織り上げられる社会全体のデザインに貢献していることを表現できます。すべての糸が同じ役割を果たしているわけではなく、それぞれの色や太さが異なり、独自の特徴があることを示しています。

社会のパズル (Society's Puzzle): この表現は、個々の人が社会全体のパズルの一片として、それぞれが持つ形状や特徴によって、適切な場所に嵌められることを示唆しています。パズルのピースはすべて異なる形をしているため、重要性の大小は関係なく、全体像を完成させるために必要な要素として表現できます。

社会のオーケストラ (Society's Orchestra): この表現は、個々の人がオーケストラの楽器奏者として、それぞれが担当する楽器やパートによって、調和の取れた音楽を奏でることを示しています。楽器奏者のそれぞれが重要でありながらも、役割や重要性が異なることを表現できます。

社会のエコシステム (Society'sEcosystem): この表現は、個々の人が生態系の中で異なる役割を果たしている生物のように、互いに影響し合いながら共存していることを示しています。生態系では、すべての生物が重要でありながら、役割や影響力が異なることが一般的です。

これらの表現は、「社会の歯車」とは異なり、個々の人が果たす役割や重要性にバリエーションを持っていることを示しています。

Permalink |記事への反応(1) | 13:38

ツイートシェア

■アメリカ海軍のトップが日本の原潜保有を支持してるんだけど

https://news.usni.org/2023/01/13/cno-gilday-expanding-military-cooperation-between-south-korea-japan-a-necessity

Any decision forJapan to build a nuclear-powered submarineis ahugestep that wouldrequire thenation’s support politically and financially for years, Gilday said. That decision must bemadewith the understanding of “the totality of theecosystem” for the initiative and thatitwilltake decades to complete.Change “eco-system” for such a projectrequires “the right people, the right training, the right platforms, the rightworkforce” and sustainment, he said.

リンク先のギルディ氏というのは現在のアメリカ海軍参謀総長(米海軍のトップ)で、この人の発言はアメリカ海軍の総意と受け取ってもいい

そんな人が公のメディアで「長い時間を要する」と前置きしつつも「日本は原潜を建造保有するべきだ」と発言してるんだけど、これ割とすごい大ニュースなのでは？

Permalink |記事への反応(0) | 00:05

ツイートシェア

■論文読んだ

The sicker the better: nematode-infected passalus beetles provide enhancedecosystem services

動物の面白い行動

https://royalsocietypublishing.org/doi/10.1098/rsbl.2018.0842

やったこと

省略

疑問・わからなかったこと

Introduction

• 仮説
  • 著者らがなぜ、この仮設を考えたのがよくわからない。想像ですが、甲虫が出した木くずは線虫の住処になっていて、線虫に利益があると考えているからだろうか？そんなことは関係なく仮説を設定したのか？

• Results
  • 非感染甲虫の方がエラーバーが大きいように見える。この中での雄とメスの差は無いのか？
  • 本当に同じ種を採取しているのか？
    • abdominal cavityの穴の大きさなどが異なることはないのか。

Permalink |記事への反応(0) | 10:21

ツイートシェア

■5 reasonswhyJapanese Engineer are fu*kingda*n

• Despite ofthe fact whichInternethasconnected people inthe world, due to thecrucial firewall -English,Japanese Engineers couldn'tjoin advanced technology discussion andcatch up latest services. Instead of that,they have just kept maintaining theiroriginalecosystem which representsashatena,Qiita andniconico.Ifit's other domains suchas "Japanesefood" or "JapanesePop Culture", then, there might bepossibility to have some valuable outcome from that. But ifit goes to "Technology" domain,it's justdamn if we goeslike that way or "Reinventing the wheel" whichdon't follow global standard andit's no value inthe world. Infact, Technologies and Services which are well known and originate fromJapan are too less inpoint of ratio ofpopulation and outcome.

• They tends totry increasing their market valueby neithergettingstarsongithubnor launch new service, but just havespeech in suchas conferences togetmore highernamerecognition.It seems they just want to weet orblog - "Givingspeech!" or "Speechdone! andnothingmore. I want tonameitas "Mounting Driven Development" - peoplewants toget better position in marketby neither codenor services but fu*kingda*nspecialized commentsonly. "衒学趣味"

• Though most of the contents thatspeech are kind of "I translated officialdocs inJapanese!", "I'vedone 'GetStarted'!",due to audienceissue whichis lacking of habits to readEnglish articles or not able to do so,it causes curious result that theyappreciate that kind ofspeech much.itgets comments suchas "I learned much fromit!", "I couldget latest knowledge!" and "Add Favorites!" andit satisfy theguywho givsspeech,tweet andblog, and motivate them to haveda*mnext post. Thoughit's justnoise forwhom usually research Primary information inEnglish,it seemsit'sstill valuable for them sinceit gives feelings to them that somewhat I understood that latest technology.

• Because theylikes "Technical document" much, though they usually study with books evenit's Front-end latest technology, Many of them are just translatedoriginal EN contents orda*n notsexy sample code,it's worthless inthe world which dynamically changingdaybyday in few months. Regardless of free latest contents which can be found everywhere, they justget Secondary Information givenby some evangelists withpassive mindset,it causes making this Evangelist? market stable due to this kind of informationgapstructure.

• They couldn't neither accepting the things abovenor justget awaredwith that withpure mindset and though doing encourage each other withsweetsmessage suchas "ManyJapanese Engineers are great andfantastic!",excellentJapanese resources ignore that kind ofdomestic industry situationand already working hard in foreign countries andit expands this bipolarizationissue worse bacause they won't have organized explanation and slides for that kind ofda*n people inJapanese and instead of that, code andmake output in a second, discuss with engineers abroad inEnglish.

See also :https://anond.hatelabo.jp/20170728223725

Permalink |記事への反応(2) | 19:23

ツイートシェア