HN user
That's a pretty cool project. But with it living in the grey area of not being really supported by Remarkable, I would be skeptical if Remarkable does not block it down the line.
Supernote has full-fledged Linux support in the official pipeline. It has gotten postponed quite recently, so the devices still run on their customized Android distribution only. But even in the current state, I feel more ownership over my HW and SW than I would with Remarkable.
I was actually thinking about buying Remarkable Paper Pro after Christmas. Not necessarily for the colors but just to have a portable e-ink tablet to scribble on and organize myself a bit better. In the end, I went with Supernote Nomad (A6X2). The build quality is not as good, the display does not have colors, and there is no backlight. But, for my use cases, it fits perfectly. I have found myself taking notes left and right, mostly during meetings.
What swayed me in the end was the software and repairability. Supernote actually released their syncing backend as a Docker image, so I can just roll my own and never have to touch any third-party cloud. All of my notes just live as normal files on my home server. The repairability is similarly open - Supernote sells all the replacement parts on their website. I guess this is the reason the build is not as nice as any Remarkable. But, for me, this sacrifice is worth it, given I plan to use the tablet as long as it can take me.
Functional programming languages (almost always?) come with the baggage of foreign looking syntax.
At least for me, this was solved by Gleam. The syntax is pretty compact, and, from my experience, the language is easily readable for anyone used to C/C++/TypeScript and even Java.
The pure approach may be a bit off-putting at first, but the apprehensions usually disappear after a first big refactoring in the language. With the type system and Gleam's helpful compiler, any significant changes are mostly a breeze, and the code works as expected once it compiles.
There are escape hatches to TypeScript/JavaScript and Erlang when necessary. But yeah, this does not really solve the impure edges many people may cut themselves on.
We've started a Tanstack Start project at work for a green field project, and it is honestly a mixed bag. It took a lot of trial and error to get the whole project working - the server parts were working without an issue, but there was no client hydration. After some debugging, we have found that there was an error being thrown during data preload which took down the hydration process. No errors were emitted, and the docs weren't were helpful at all.
But once we got that out of the way, it is pretty nice to work with. The FE developer is very happy with how fast the project is and how easy it is to just peek into the BE portion and understand it. Server functions are just so nice to use and everything gels together really well. But it's still early days though. I would only recommend it if you are OK with parsing not-really-great documentation and maybe some relevant GitHub issues from time to time.
Yeah, I would expect something in that vein. I think the pros outweigh the sluggishness of desktop rearrangement or non-existent updates. Maybe I would finally get into some driver development if it became my main machine.
Thanks a lot! I'll give it a chance once I have some time.
I have been thinking of going down the Linux route on my 2017 15". But I am unsure if it is even feasible to get it up-and-running with the T2.
With the new ARM processors the discontinuation of support for Intel-based machines is just a question of time even though the hardware is still more than capable.
Employee protection. Just because the management could not balance the sheet is not a good enough reason employees should suffer the consequences. At least in theory.
But if the company is shutting down a whole team without replacement, the employees should still get the option to relocate into another role. They can be let go only after that fails.
Yes, Slavic languages have similarities. The same could be said for Germanic languages like English and German or Latin languages like Spanish and Portuguese.
That doesn't change the fact that the word "robot" in the meaning of artificial human was first used in R.U.R.
It's funny to see how languages branch out and develop independently. I specifically remember that Czech "Šukat drogy na záchodě", which means "To fuck drugs on the toilet", would be "Look for medicine in the west" in Polish. I'm not 100 % sure that the Polish is right but it shows pretty well how large the overlap between Slavic languages there is. And also how many false friends we have.
It might have to do with the Czech National Revival[1]. The Czech language and culture was being suppressed in favour of Austrian/Germanic one. Prominent Czech figures worked to preserve the Czech language which included distancing from German words and phrases, redefinition of words and even invention of new ones.
It was pretty much a success and we ended with what could be called Czech 2.0. How many false friends were introduced because of the Revival, I am not sure.
Native speaker here, you are absolutely right. Work in Czech would be "práce", "robota" means forced work. It is not used as much nowadays since we do not live in a feudal society anymore though :)
I mean, they could ideally go PC and Stadia (since it is basically PC with fixed specs) -> Xbox One/PS4 -> Xbox Series/PS5. It wouldn't hurt the contract with Google and it would help with the terrible technical state on consoles.
I've personally tried the game on Xbox One X and only problems I've found were graphical glitches but it still is not a great experience. It's honestly pretty sad it ended like this with the amount of crunch and the token system the developers had.
The whole project feels terribly mismanaged. Even from the character editor it is obvious the game had to be scaled down in the last year to even ship. Considering the amount of crunch, it is heartbreaking it ended like this for every interested party.
I find it hard to believe that the launch of the new consoles did not have an effect on the launch date. CD Projekt could have taken the Rockstar approach, release the game on the last gen or PC and Stadia first, then polish and release on the second platform and then finish with the next gen. Releasing on seven or more platforms at the same time would not go well even before covid.
You have invested a lot of time into PHP and can make a living out of it. More power to you!
But from my anecdotal experience not many new developers invest the time to learn PHP. At the two universities I've been to, PHP is usually one and done thing. You take one course or just a few lessons with PHP in web development class and then move on to other things.
Which of these new websites have large userbase? Anyone can start their Wordpress blog with some limited free hosting and thus increase Wordpress market share. And since internet has grown considerably in the last 10 years more people tried to make their own website. And with Wordpress that is incredibly easy for people who are not technologically inclined.
Sure, websites like TechCrunch, BBC, Playstation Blog or Variety use it but they have done so for a long time. Newer websites/companies are not using Wordpress and maybe not even PHP. Medium runs on combination of Node and Go, Twitch has gone with Ruby on Rails among others, Trello runs on MongoDB and CoffeeScript on the frontend and I could go on.
I really can't think of any green field project that would be started with PHP today. Maybe if there is some specification to use something PHP specific. But any use case I can think of, Python or node is a better choice. Maybe even Java. And Rust is on the rise now, in case speed is needed. PHP isn't dead yet. But it definitely is not growing.
Also arguing that choosing a language based on ugliness is a stupid idea is a stupid idea on itself. Quality of life during development is not an insignificant thing. The resulting project will suffer greatly if the chosen language makes me want to tear my hair out.
Apple have stated multiple times that they don't have any intention to lock down macOS more or less
What Apple says and Apple does can or are two different things. And it applies to any company in the world. Blindly believing them is naive at best.
I can't really think why anyone would think Apple would lock down macOS
I can think of one: iOS. Locking down the software and hardware can allow Apple to funnel people to their own stores and services. It is not rocket science to figure out that a company is trying to increase their revenue. Right now you have only MacOS as the operating system, Linux may never come and Windows support is anyones guess right now.
As usual, it really comes down to personal preference. In the past year, I have managed a few things in Wordpress, wrote my own PHP, Flask and node sites; and after all that I would 100 % choose Flask or node over PHP.
Node has the advantage of same language back and front, "asynchronous" execution and having both dynamic typing and static typing with TypeScript. And huge ecosystem obviously helps as well.
Python also has pretty sizeable community and Django is probably a huge reason why a lot of people choose python over anything else. And the syntax, at least to me, feels much less cumbersome than PHP. But I have not tried PHP 8 at all.
Same here. Maybe it is one of the anti-GDPR mechanisms? Rather than be sure you are compliant or do not want to be compliant, just prevent EU citizens from connecting. Or maybe the site is just down and I am over thinking this.
Thanks, that makes sense and I probably should have looked into the article properly.
I'm not sure, how easy it will be to filter the devDependencies. Maybe scan for config files (webpack, babel...) would be a good alternative to manually tag each npm package.
Isn't this already done by Dependabot[1]? I've been using it for some time with my JS/TS repos to keep my dependencies up-to-date. It's not the greatest as it sends alerts about vulnerabilities in devDependencies. But with automatic merge checks I only get an email that the issue has been fixed so it isn't the worst thing in the world.
Actual REST is least useful for communication between a single frontend and backend controlled by the same party.
I know I'm going off-topic but what is best way to communicate between frontend and backend except for REST? I know about GraphQL even though that is not widely adopted yet and in a lot of cases never will be.