Shakedown Social

cst1<a href="https://a.gup.pe/u/academicchatter" class="u-url mention" rel="nofollow noopener" target="_blank">@academicchatter</a> Okay, what tools would you recommend using to help order, browse, visualize and expand your research library? I'm using Zotero as the backing library manager + <a href="https://researchrabbitapp.com/" rel="nofollow noopener" translate="no" target="_blank">https://researchrabbitapp.com/</a> for the visualization/discovery part but open to suggestions and tips!<a href="https://chaos.social/tags/academia" class="mention hashtag" rel="nofollow noopener" target="_blank">#academia</a> <a href="https://chaos.social/tags/phd" class="mention hashtag" rel="nofollow noopener" target="_blank">#phd</a> <a href="https://chaos.social/tags/research" class="mention hashtag" rel="nofollow noopener" target="_blank">#research</a> <a href="https://chaos.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#compsci</a>

Aether~Fedi, I have a <a href="https://plasmatrap.com/tags/ComputerScience" rel="nofollow noopener" target="_blank">#ComputerScience</a> (maybe <a href="https://plasmatrap.com/tags/Linguistics" rel="nofollow noopener" target="_blank">#Linguistics</a> ?) Question I need your lovely guidance for ❤️:boosts_ok_gay:💙 I have a design problem about grammar ambiguity ish stuff and want to find reading, resources or theory I can check out to come up with an elegant solution. Particularly, I'm trying to find good alternatives to cases when a given word can appear in multiple parts of the syntax An example problem (sorry it's very computery): I have two strings (or lists of tokens) I need to combine into a single string, separated by a delimiter, such that both strings can be retrieved again. But, that delimiter can show up in either of the two strings. The standard way to deal with this is to designate an escape token and prepend all instances of the delimiter within the strings with it (eg <code>\"</code>). The issue there is now is that any instances of the escape token need escaping too (e.g. <code>\\</code>). Slightly less work is inserting a repetition of the delimiter any non-delimiting instances of the token. If the delimiter appears twice, it's part of a string, and the only non-repeating delimiter must be the real one. This can look ugly if the delimiter is long though. Another crazy option would be interlacing the two strings so all even tokens belong to string 1 and odd ones are string 2. This would obviously look horrible, but maybe there are other solutions taking a similar thought process. That's just the most basic case I'm interested in, there might be heaps of other strategies when you have more restrictions and guarantees on what the tokens might contain. So yeah I'm looking for stuff like that so I can figure out good patterns for unambiguous yet elegant grammars. For a tad more context, I'm thinking about command line argument formats, trying to think of the most user friendly ways to handle complex data as a list of arguments. Also please boost and let me know if there's hashtags I should include etc :ablobcatheart: <a href="https://plasmatrap.com/tags/CompSci" rel="nofollow noopener" target="_blank">#CompSci</a> <a href="https://plasmatrap.com/tags/programming" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://plasmatrap.com/tags/askfedi" rel="nofollow noopener" target="_blank">#askfedi</a> <a href="https://plasmatrap.com/tags/TechSupport" rel="nofollow noopener" target="_blank">#TechSupport</a> <a href="https://plasmatrap.com/tags/CompSci" rel="nofollow noopener" target="_blank">#CompSci</a> <a href="https://plasmatrap.com/tags/programming" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://plasmatrap.com/tags/askfedi" rel="nofollow noopener" target="_blank">#askfedi</a> <a href="https://plasmatrap.com/tags/TechSupport" rel="nofollow noopener" target="_blank">#TechSupport</a>

vruzDirect WASM→DOM access doesn't leave JavaScript behind - JS could use the same fast path! We could even build Fagnani's exact templating API as a reference implementation on top of it. But unlike a JS-only solution, the platform stays open for potentially superior approaches in ANY language. Rust might build something faster. Zig might build something smaller. That's the kind of competition through collaboration that drives innovation. Everybody wins wins wins. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#compsci</a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://mstdn.social/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#wasm</a> <a href="https://mstdn.social/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#javascript</a>

vruzWeb's superpower is its openness. Native JS templating makes JS more ergonomic. Direct WASM→DOM makes the web more OPEN. Which better serves the platform's future? The web shouldn't privilege one language. True platform evolution means equal access to core capabilities for all languages. That's how we get the next generation of web innovation. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#compsci</a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://mstdn.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#webstandards</a> <a href="https://mstdn.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a>

vruzInstead of standardizing one templating syntax (that'll be bikeshedded to death), give us the primitive: fast DOM access from any language. Let a thousand templating libraries bloom - in any language. Lower-level primitives enable more innovation than high-level APIs. That's the Unix philosophy. Simple, composable, powerful. Build the foundation right. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#compsci</a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://mstdn.social/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#wasm</a> <a href="https://mstdn.social/tags/frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#frontend</a> <a href="https://mstdn.social/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a>

vruzFrameworks already solved templating. They're good at it! What they CAN'T solve is the JS monopoly on DOM access. Open that up and watch innovation explode across the entire ecosystem. React, Vue, Svelte - they all work great. But imagine what could be built if any language had direct DOM access. New paradigms, new approaches, new frameworks we can't even conceive of yet. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#compsci</a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://mstdn.social/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#javascript</a>

vruzThe performance argument for native templating is weak - we're talking 2% gains, max. But remove the JS bridge for WASM? That's where real performance wins live. Fix the actual bottleneck. Every DOM call through JS is overhead we don't need. Direct access would unlock true native speeds for web UIs. Imagine game engines manipulating DOM at 60fps without JS overhead. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#compsci</a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://mstdn.social/tags/performance" class="mention hashtag" rel="nofollow noopener" target="_blank">#performance</a> <a href="https://mstdn.social/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#wasm</a>

vruzThe Web's superpower is its openness. Native JS templating makes JS more ergonomic. Direct WASM→DOM makes the web more OPEN. Which better serves the platform's future? The web shouldn't privilege one language. True platform evolution means equal access to core capabilities for all languages. That's how we get the next generation of web innovation. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#compsci</a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://mstdn.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#webstandards</a> <a href="https://mstdn.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a>

vruzNative JS templating: helps JavaScript developers. Direct WASM→DOM: helps EVERY language. Rust, Go, C#, Zig, Swift, Kotlin... all get first-class web UI performance. That's real platform evolution. We shouldn't be adding more JS-specific APIs when we could be opening the web to all languages equally. The web platform should be language-agnostic at its core. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#compsci</a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://mstdn.social/tags/webassembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#webassembly</a> <a href="https://mstdn.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a>

vruzWhy add yet another JS templating API when WASM + direct DOM access solves the root problem? Every language could build efficient UIs without the JS bottleneck. More universal than blessing one syntax. Think beyond JavaScript - imagine Rust components with zero overhead, Go templates that actually perform, or C# Blazor without the bridge tax. That's true platform evolution. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#compsci</a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://mstdn.social/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#wasm</a> <a href="https://mstdn.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#webstandards</a>

vruzSome people still weren't born, or came of age recently and are building the future, but never before had the luxury afforded to them and they have never known a world without React, or a world with non-stupidly complex technology so they keep reinventing things like Mustache.<a href="https://mstdn.social/tags/mustachejs" class="mention hashtag" rel="nofollow noopener" target="_blank">#mustachejs</a> <a href="https://mstdn.social/tags/mustache" class="mention hashtag" rel="nofollow noopener" target="_blank">#mustache</a> <a href="https://mstdn.social/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#javascript</a> <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#compsci</a> <a href="https://mstdn.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://mstdn.social/tags/tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#tech</a> <a href="https://mstdn.social/tags/technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#technology</a>

Ele Willoughby, PhDHappy birthday to Alan Turing, OBE, FRS (1912 – 1954), British <a href="https://spore.social/tags/mathematician" class="mention hashtag" rel="nofollow noopener" target="_blank">#mathematician</a>, <a href="https://spore.social/tags/cryptanalyst" class="mention hashtag" rel="nofollow noopener" target="_blank">#cryptanalyst</a>, computer scientist, prophet & hero. Turing foresaw not only that machines might quite likely develop the capacity to think (after all, our brains are only made of matter, and complex systems of neurons, which either fire or not, much like an electronic switch), but that we needed an objective, double-blind test to determine whether 🧵1/n<a href="https://spore.social/tags/sciart" class="mention hashtag" rel="nofollow noopener" target="_blank">#sciart</a> <a href="https://spore.social/tags/printmaking" class="mention hashtag" rel="nofollow noopener" target="_blank">#printmaking</a> <a href="https://spore.social/tags/linocut" class="mention hashtag" rel="nofollow noopener" target="_blank">#linocut</a> <a href="https://spore.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#compsci</a> <a href="https://spore.social/tags/histsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#histsci</a> <a href="https://spore.social/tags/mastoart" class="mention hashtag" rel="nofollow noopener" target="_blank">#mastoart</a>

Rachel Wil Singh ~ Moos-a-deeInstead of using LibreOffice Calc to track student progress throughout the semester, I've figured out how to use GnuPlot. >:3(X-axis: Week of summer class; Y-axis: grade in the class. All assignments start at 0% and as they complete work their grade goes up.)<a href="https://mastodon.gamedev.place/tags/CompSci" class="mention hashtag" rel="nofollow noopener" target="_blank">#CompSci</a> <a href="https://mastodon.gamedev.place/tags/Education" class="mention hashtag" rel="nofollow noopener" target="_blank">#Education</a>

Rachel Wil Singh ~ Moos-a-dee<a href="https://www.youtube.com/watch?v=Y9BspntZHok" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=Y9BspntZHok</a>I Taught a Kids' Gamedev Class Using Tic-80 Fantasy Computer<a href="https://mastodon.gamedev.place/tags/Tic80" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tic80</a> <a href="https://mastodon.gamedev.place/tags/CompSci" class="mention hashtag" rel="nofollow noopener" target="_blank">#CompSci</a> <a href="https://mastodon.gamedev.place/tags/Education" class="mention hashtag" rel="nofollow noopener" target="_blank">#Education</a>

LobstersAstonishing discovery by computer scientist: how to squeeze space into time <a href="https://lobste.rs/s/an5g0c" rel="nofollow noopener" translate="no" target="_blank">https://lobste.rs/s/an5g0c</a> <a href="https://mastodon.social/tags/video" class="mention hashtag" rel="nofollow noopener" target="_blank">#video</a> <a href="https://mastodon.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#compsci</a> <a href="https://www.youtube.com/watch?v=8JuWdXrCmWg" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=8JuWdXrCmWg</a>

Lisp & Scheme WeeklyThe next phase of jank's C++ interop<a href="https://jank-lang.org/blog/2025-06-06-next-phase-of-interop/" rel="nofollow noopener" translate="no" target="_blank">https://jank-lang.org/blog/2025-06-06-next-phase-of-interop/</a>Discussions: <a href="https://discu.eu/q/https://jank-lang.org/blog/2025-06-06-next-phase-of-interop/" rel="nofollow noopener" translate="no" target="_blank">https://discu.eu/q/https://jank-lang.org/blog/2025-06-06-next-phase-of-interop/</a><a href="https://mastodon.social/tags/clojure" class="mention hashtag" rel="nofollow noopener" target="_blank">#clojure</a> <a href="https://mastodon.social/tags/compilers" class="mention hashtag" rel="nofollow noopener" target="_blank">#compilers</a> <a href="https://mastodon.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#compsci</a> <a href="https://mastodon.social/tags/cpp" class="mention hashtag" rel="nofollow noopener" target="_blank">#cpp</a> <a href="https://mastodon.social/tags/plt" class="mention hashtag" rel="nofollow noopener" target="_blank">#plt</a> <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a>

Richard DeadmanI retired from my work architecting computer systems this week and went out to dinner to celebrate. My waitress was a recent Computer Engineer grad struggling to find a job in her field.I'm skeptical about AI but do think jobs are being lost due to over-promoting it to depress wages and companies drinking the AI kool-aid."Learn to Code" Backfires Spectacularly as Comp-Sci Majors Suddenly Have Sky-High Unemployment <a href="https://futurism.com/computer-science-majors-high-unemployment-rate" rel="nofollow noopener" translate="no" target="_blank">https://futurism.com/computer-science-majors-high-unemployment-rate</a><a href="https://mastodon.online/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#compsci</a> <a href="https://mastodon.online/tags/ai" class="mention hashtag" rel="nofollow noopener" target="_blank">#ai</a>

Recent searches

Search options

Administered by:

Server stats:

#compsci