HackerTrans
トップ新着トレンドコメント過去質問紹介求人

alasr

no profile record

投稿

OpenJDK: Removal of the JVM Compiler Interface (JVMCI), in JDK 27

bugs.openjdk.org
4 ポイント·投稿者 alasr·先月·2 コメント

Playing Doom on a SUBLEQ Transformer

xcancel.com
1 ポイント·投稿者 alasr·4 か月前·1 コメント

Loophole found that makes quantum cloning possible

newscientist.com
2 ポイント·投稿者 alasr·5 か月前·0 コメント

OpenSSL v3.6.1

github.com
1 ポイント·投稿者 alasr·5 か月前·0 コメント

The Dark Side of the AI Boom Is It’s Masking Weak Investment

bloomberg.com
3 ポイント·投稿者 alasr·9 か月前·1 コメント

Small Language Models Are the Future of Agentic AI

research.nvidia.com
2 ポイント·投稿者 alasr·10 か月前·0 コメント

コメント

alasr
·30 日前·議論
> Why does it need to be beautiful?

"Beauty", IMO, signifies the idea that you're doing `something` for its own the sake where "its own sake" approximate the idea of getting/being closer to (or in proximity of) `something`/`anything`/`someone` you find "beautiful".

> Once you proved it it's true and you can use its consequences in math, sciences and engineerings (sic).

The expression "you can use its consequences in ..." suggests that the action is a "just a means" to "something else". However, not everyone is interested in the idea of "something else"; they're interested in the idea itself (in a broad sense) as that's one of the main reason they got started/involved in the first place.

---

We all do things as "just a means" to "something else". However, there must be an "end" to this chain of "something else"; otherwise, how do you find any "meaning" (or sense of fulfillment) in this whole enterprise (or chain of "something else"s)?
alasr
·先月·議論
Regarding the the current HN post's title, I like the TFA original title ("The New 20% Time, Minus the Time") better, along its sub-title; IMHO, the current HN post's title ("Google's 20% 'project' has become AI's 120% 'attention'") is more like reflection of the HN submitter's interpretation of the content of the blog post (that I agree with partially and to a small/negligible extent ONLY).

---

IMO, keeping "Google 20% Time" (mentioned in the TFA) and "R&D is two jobs, ..." (his second-last blog post, at time of writing this comment) in mind while reading this blog post, helps in reading and understanding the content of this blog post; whether we agree (or not) with the author's point-of-view is another matter.

---

Btw, I also noticed AI usage on this blog post; however, I over-looked that part of the post after looking at author's past work (and I'm happy I did that and continued reading the post).
alasr
·4 か月前·議論
GitHub repo.: https://github.com/kfoynt/neural_doom
alasr
·4 か月前·議論
Just a small nitpik with the following part of your post.

> As the paper suggests: ...

This is not a paper; it's just a blog post which is mentioned in this post's URL (i.e. .../blog/can-llms-be-computers).

Also it, at the end of the article, has a job advertisement (nothing unusual for a blog post):

    "We are building these systems now, and we are hiring. If you want to work on problems at ..., join us."
alasr
·5 か月前·議論
I think you're reading the docs correct: one still uses "lms server [command]" command to manage an LM Studio (LMS) server.
alasr
·5 か月前·議論
> What exactly is the difference between lms and llmsterm?

With lms, LM Studio's frontend GUI/desktop application and its backend LLM API server (for OpenAI compatibility API endpoints) are tightly coupled: stopping LM Studio's GUI/desktop application will trigger stopping of LM Studio's backend LLM API server.

With llmsterm, they've been decoupled now; it (llmsterm) enables one, as LM Studio announcement says, to "deploy on servers, deploy in CI, deploy anywhere" (where having a GUI/desktop application doesn't make sense).
alasr
·6 か月前·議論
> I think I kind of have an idea what the author was doing, but not really.

Me neither; However, just like the rest I can only speculate (given the available information): I guess the following pieces provide a hint what's really going on here:

- "The quine is the quine" (one of the sub-headline of the article) and the meaning of the word "quine".

- Author's "scaffolding" tool which, once finished, had acquired the "knowledge"[1] how to add a CLAUDE.md baked instructions for a particular homemade framework (he's working on).

- Anthropic saying something like: no, stop; you cannot "copy"[1] Claude knowledge no matter how "non-serious" your scaffolding tool or your use-case is: as it might "shows", other Claude users, that there's a way to do similar things, maybe that time, for more "serious" tools.

---

[1]. Excerpt from the Author's blog post: "I would love to see the face of that AI (Claude AI system backend) when it saw its own 'system prompt' language being echoed back to it (from Author's scaffolding tool: assuming it's complete and fully-functional at that time)."
alasr
·8 か月前·議論
I haven't used any LLM deep research tools in the past; today, after reading this HN post, I gave Tongyi DeepResearch a try to see how it performs on a simple "research" task (in an area I've working experience in: healthcare and EHR) and I'm satisfied with its response (for the given tasks; I, obviously, can't say anything how it'll performs on other "research" tasks I'll ask it in the future). I think I'll keep using this model for tasks for which I was using other local LLM models before.

Besides I might give other large deep research models a try when needed.
alasr
·9 か月前·議論
https://archive.is/lgDXT
alasr
·9 か月前·議論
Regarding C# and Java part of your comment, I think you might want to take a look at the following Wikipedia entries:

- Microsoft Java Virtual Machine: https://en.wikipedia.org/wiki/Microsoft_Java_Virtual_Machine

- Visual J++: https://en.wikipedia.org/wiki/Visual_J%2B%2B