samuelstros

9 ms·

61.
by samuelstros 2y ago
Did that, done that. Check out https://inlang.com/m/tdozzpar/app-inlang-finkLocalizationEdi... We are going to switch the approach from opening git repos in the browser to a new "version control" system
62.
by samuelstros 2y ago
Isn't sending an email publishing (in version control terms CI/CD deployment)?
63.
by samuelstros 2y ago
Things we discussed: - a commit is somewhat a 'save' but unlike a 'final_v1.docx' - a commit prevents changes from being overwritten
64.
by samuelstros 2y ago
Doesn't make click for me. Snapshot is a VCS term that seems to have a different meaning in photography. From Wikipedia "A snapshot is a photograph that is "shot" spontaneously and quickly, most often without artistic or
65.
Ask HN: How would you describe a commit?
1 points by samuelstros 2y ago|6 comments
66.
by samuelstros 2y ago
disclaimer: i'm the founder of https://inlang.com/ monetizing your solution will likely be a dead end. the value prop of your solution doesn't match the app you built, and what buyers pay for. for example, machine
67.
by samuelstros 2y ago
> translation infrastructure built around .PO files not only .po files :D XML, i18next json, localizable strings (iOS), ... the list goes on.
68.
by samuelstros 2y ago
if conflict resolution has to happen in the network layer -> tbd. it seems like apps that have built-in conflict resolution can resolve conflicts. zip archives will play a role. i am pushing for "zipped repositories" internally
69.
by samuelstros 2y ago
I refer to open source projects, indie hackers, and one man shows with "hobby apps." Distribution (specifically maintenance) becoming cheaper will enable those people to compete/provide enough value to customers that larger c
70.
by samuelstros 2y ago
> The issue comes when end-users expect the same level of support and continued updates from hobbyists as they got from commercialized apps. Maybe. Doesn't change the fact that software will be more commoditized. If software switchi
71.
by samuelstros 2y ago
Yep. Local-first is further commoditizing software. Users will refrain from paying a subscription if their app version works and they don't need updates. The good old buy-a-license with 1 year of updates will likely make a big comeback
72.
by samuelstros 2y ago
> Can't wait for the next cycle. Edge compute :D Have data distributed "wherever" (client, server) to perform computations "wherever". Using a video editor as an example: The video editor running locally means vi
73.
by samuelstros 2y ago
A universal sync engine could be "files as zipped repositories." A repository as a file is self-contained, tracks changes by itself, and is, therefore, free from vendor lock-in. Here is my draft RFC https://docs.google.
74.
by samuelstros 2y ago
big picture is that cloud-based apps/saas is getting disrupted. there is no value in a cloud-based solution that locks users and customers in if collaboration can be solved in the data (file) level. turns out that version control solve
75.
by samuelstros 2y ago
here, be blown away https://github.com/opral/monorepo/tree/main/lix solving version control for files like jupyter notebooks brings collaboration to those files without the need to give up files in favor
76.
by samuelstros 2y ago
"seeking a price of between $750M and $1B"
77.
by samuelstros 2y ago
> what will get developers to start building with lix vs. what they know/trust? 1. the ease of building an app 2. the additional features like change history, ai readiness, etc. that cloud-backends like supabase or firebase don&#x27
78.
by samuelstros 2y ago
Hi hn crowd, founder of opral here. we seem to have stumbled on an easier and better way to build collaborative apps by leveraging "version control as a backend": - collaboration for file-based software (a real-time layer can be a
79.
Our seed memo to build a change control system and SDK(docs.google.com)
10 points by samuelstros 2y ago|4 comments
80.
by samuelstros 2y ago
You seem to mix corporate vs personal taxation. Personal taxation is always your country of residency. If you hold stock in an EU Inc., the capital gains tax in your country of residency would apply.
81.
by samuelstros 2y ago
> The problem with the EU wide Inc, is who gets the tax revenue? Every country proportional to the profit they generate and the tax rate they set? Companies overall EU profit $100M: - France $30M profit taxed at 20% = $6M - Germany $50M
82.
Git as a backend is an easy way to build collaborative apps(youtube.com)
6 points by samuelstros 2y ago|3 comments
83.
by samuelstros 2y ago
This internal demo might be of interest to the HN crowd. We are building a git-like change control system called lix that can store different file formats. Why? - file-based software is amazing because of interop and data ownership - storin
84.
by samuelstros 3y ago
What's the value to users if you are NextJS based? - internal tools rarely (never?) need SEO - the complexity of NextJS rings alarm bells as infra product. A look at your docs confirms my suspicion https://docs.trycreo.com&#
85.
by samuelstros 3y ago
the reason is less knowing our audience and more "it was just easier [than setting up a careers page]" :D
86.
by samuelstros 3y ago
Great feedback. I'll forward it to Nils, who is responsible for communication. Reply from him should follow on Monday
87.
by samuelstros 3y ago
> That at least tells me who is the buyer and what benefit I will get That is our problem. Taking a software product global (i18n/localiation/marketing) targets multiple personas and buyers (managers, developers, translators, d
88.
by samuelstros 3y ago
What is unclear? we know that we haven't nailed communication yet. one team member is working full time on communication/the website
89.
by samuelstros 3y ago
fixed the capitalization https://github.com/opral/monorepo/commit/6127c6899290b35442c...
90.
by samuelstros 3y ago
thanks. do you understand what inlang is by looking at the site?

More ›