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.
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.
If they do though then I won't update and won't buy the next model. I can imagine them doing it for a new model for already sold one that'd be a first.
FWIW if you really want ownership and don't care much for weight the PineNote is probably the best our there, able to run Android (with root) but also Linux proper.
> 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.
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.
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.
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.
The word 'robota' is also related to the German word 'arbeiter'; both suggesting 'laborer' at the most basic level, and sometimes used as a euphemism for outright slave.
Thus the ironic power of the word's use in the play, the same irony that powers the motto 'Arbeit Macht Frei'.
"Robotnik" is still used in Polish to mean someone who does manual labor and the like. The pejorative "robol" translates as "prole" as in "proletarian".
When Capek created word robot using robotnik as a base, the term was not used for close to 200 years. Czech translation of robotnik in Polish would be delnik.
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.
In this article [1] i see quite a lot of funny examples of false friends for czech to russian translation. Stale is cherstvyj in russian, but in czech cherstvyj is fresh. A corpse in russian is a torso in czech. Shame is attention. A cigarette butt is a cucumber. Toadstool is buckwheat. Looseness is speed. And so on. Some words like zivot in czech are closer to old russian meaning (life) than current (stomach). Between some i can see some other relation. And with some i have no idea how it could coincide that way.
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.
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 :)
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.
I do get a sense of mismanagement as well, however the platform situation is a bit complicated.
Stadia release was probably contractually obligated to happen with the first volley. It was a big bet for Google, they never shut up about how Cyberpunk will come out for Stadia. Based on a few reviews I've read, the Stadia version seems to have turned out OK.
The PS5/SeriesXS versions are coming out in 2021. They don't exist right now. The reason the game runs on PS5/SeriesXS is backwards compatibility. That backwards compatibility didn't exist at the time when GTA5 was released for PS3/Xbox360.
The PS4/XBoxOne versions of Cyberpunk should have definitely been delayed. However I think it's not just the holiday season that is a factor here. It's also that the new generation of consoles already came out. Rockstar managed to get GTA5 out for PS3/Xbox360 a few months before PS4/XBoxOne.
It's clear that the PC version was the focus for CDPR - as it has always been for its games. It would have helped to schedule the PC version for later (like Rockstar scheduled GTA5 for PC - 2 years after PS3/XBox360) so that initially the focus could be on PS4/XBoxOne - it would probably have resulted in better reviews and a way more polished game. However ignoring PC for so long can be a hard pill to swallow for a PC centric developer - and indeed, they chose not to do it. According to the Q&A PC pre-orders made up 59% of their sales, so from a sales perspective delaying PC probably not the best choice either.
--
I do wonder how the PS4/XboxOne version of Cyberpunk looked 6 months ago and how much progress has there been. Hard to imagine it being way worse, but if it has been consistently so bad then it's puzzling why there wasn't significant steps taken as the quality of the game on those platforms wasn't changing.
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.
release the game on the last gen or PC and Stadia first
It is only released on last gen consoles. There's no native PS5 or Xbox series X/S version you can buy. You buy the PS4/Xbox One version and play it via backwards compatibility. Apart from video resolution or low FPS, have there been significant problems on the last gen consoles in terms of bugs that aren't on the new gen?
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.
I have started one side project , and one startup this last 3 month, all in php/symfony, though I have made extensive use of python (and php) in the past (and do a lot of rust on the side)
1. A mature ecosystem: Symfony is really really mature, all use case of a classic website are covered:
* easy "admin" generation -> check
* easy styling of your forms (a guy already made a 'tailwind' template, now I just do {{ form(my_form }}, and that's it
* easy integration with webpack for my usecase with tailwind
* pretty fast load to the point that the backoffice feels like a SPA (no flickering)
* word-class ORM (Doctrine is just the best ORM ever, they really got right the 'if you know SQL, you will not have to learn yet an other dialect, all our functions/method use the exact same naming as in SQL , take that django ORM)
* once again word-class ORM (Doctrine make it very easy to use all postgres-only, or mind you, mysql-only feature, DATE_TRUNC , json operators, full-text search operators etc. etc.)
* The documentation is not only encyclopedic , but also 'cookbook' (i.e you can either go A to Z, or they have dedicated article "how to have 2 database" , "How to implement a login through JSON" , which are much better and up to date than googling "how to X with framework Z"
2. PHP type system, sorry python but mypy just doesn't make it, I love my typechecking at runtime, how many times good willing developers in python have put `def myfunction(something: dict)` but it was actually not a dict, but a generator, and boom the next dev is mislead and introduce a bug
3. easy as hell to find developers, developers that likes to get things done and that are pragmatic (They know, I know, we all know PHP have shortcomings, do we joke about it? yes. Does it prevent us from moving forward ? no)
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.
I also got the same kind of class, I think php was a 2 week class (less than the Java courses or SQL courses, same as the ASM courses).
a 2/3 of my career was python, I 2~3 years of PHP around 2011-2014, and now I'm using it back as I'm finally doing my own company.
And the best part of it ? It's right where I left it, even thought it went from 5.4 to 8 , and from symfony 2 to 5. It feels like leaving your old band from college to find out you all have the same habits, just everyone improved along the road.
Regardless how much I like python, to have been the one needing to own the "python2 to 3 migration" projects of 3 companies, it was not pretty.
Market share of WordPress as website platform in 2011 : 13%
In 2020 : 38%
Yeah, php is not growing. Growing might start to become difficult when you en 40% of the web.
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.
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.
reply