Beiträge, die mit update getaggt sind
HN Discussion: https://news.ycombinator.com/item?id=19443925
Posted by SamuelAdams (karma: 366)
Post stats: Points: 265 - Comments: 250 - 2019-03-20T16:39:22Z
#HackerNews #after #again #barriers #drives #fine #months #software #tesla #update #working
HackerNewsBot debug: Calculated post rank: 260 - Loop: 456 - Rank min: 100 - Author rank: 53
Linux 5.0 ist da: Geschwindigkeit zurückerobern und moderner speichern | c't Magazin
Linux 5.0 ist da: Geschwindigkeit zurückerobern und moderner speichern
Don't think this whole thing is just a flash in the pan, because it's not. I can't sustain the blitz of last weekend's rebel postings. That was the summation of a long term plan and a weeks nights on the GIMP doing the #ArtHarder to produce graphics. Even though the frequency of Rebel postings might slow a little, rest assured this alliance is here to stay and will remain a permanent addition to the diaspora* landscape. Slow and steady is the pace.
As expected, the opposition has been relentless but we are thankful for our many supporters, both overt and covert. You know who you are. ;) I appreciate you all, when things seem dark and I start to feel demoralized, you guys lift me up and give me hope. I am eternally grateful for that. The opposition posts reek of desperation, and their talking points are tired and redundant. Our future is looking bright.
In the near future there are more rebel posts planned. I intend to release a bunch of the badges and flags I've made as CC creative commons, so that the d* community can freely use them. Also I am noticing a lot of the same comments and questions are being repeatedly asked, so I plan on putting together a Rebel Alliance FAQ post.
So stay tuned true believers, there is much more to come.
#Thanks #Appreciation #Gratitude #Perseverance #Network #SocialMedia #Federation #Community #GrassRoots #Public #Pub #Freedom #FC #FreedomClub #Motivational #Hope #NeverGiveUp #NoSurrender #qotd #uncleTed #Inspiration #Gunday #SKS
We announced our React Native Open Source roadmap in Q4 2018 after deciding to invest more in the React Native open source…
Article word count: 852
HN Discussion: https://news.ycombinator.com/item?id=19286335
Posted by cpojer (karma: 1285)
Post stats: Points: 134 - Comments: 51 - 2019-03-01T23:32:48Z
#HackerNews #native #open #react #source #update
We announced our React Native Open Source roadmap in Q4 2018 after deciding to invest more in the React Native open source community.
For our first milestone, we focused on identifying and improving the most visible aspects of our community. Our goals were to reduce outstanding pull requests, reduce the projectʼs surface area, identify leading user problems, and establish guidelines for community management.
In the past two months, we made more progress than we expected. Read on for more details:
In order to build a healthy community, we must respond quickly to code contributions. In past years, we de-prioritized reviewing community contributions and accumulated 280 pull requests (December 2018). In the first milestone, we reduced the number of open pull requests to ~65. Simultaneously, the average number of pull requests opened per day increased from 3.5 to 7 which means we have handled about 600 pull requests in the last three months.
We merged almost two-thirds and closed one-third of the pull requests. They were closed without being merged if they are obsolete or low quality, or if they unnecessarily increase the projectʼs surface area. Most of the merged pull requests fixed bugs, improved cross-platform parity, or introduced new features. Notable contributions include improving type safety and the ongoing work to support AndroidX.
At Facebook, we run React Native from master, so we test all changes first before they make it into a React Native Release. Out of all the merged pull requests, only six caused issues: four only affected internal development and two were caught in the release candidate state.
One of the more visible community contributions was the updated “RedBox” screen. Itʼs a good example of how the community is making the developer experience friendlier.
React Native currently has a very wide surface area with many unmaintained abstractions that we do not use a lot at Facebook. We are working on reducing the surface area in order to make React Native smaller and allow the community to take better care of abstractions that are mostly unused used at Facebook.
In the first milestone, we asked the community for help on the Lean Core project. The response was overwhelming and we could barely keep up with all the progress. Check out all the work completed in less than a month!
What we are most excited about is that maintainers have jumped in fixing long standing issues, adding tests, and supporting long requested features. These modules are getting more support than they ever did within React Native, showing that this is a great step for the community. Examples of such projects are WebView that has received many pull requests since their extraction and the CLI that is now maintained by members of the community and received much needed improvements and fixes.
Leading User Problems
In December, we asked the community what they disliked about React Native. We aggregated the responses and replied to each and every problem. Fortunately, many of the issues that our community faces are also problems at Facebook. In our next milestone, we plan to address some of the main problems.
One of the highest voted problems was the developer experience of upgrading to newer versions of React Native. Unfortunately, this is not something that we experience ourselves because we run React Native from master. Thankfully, members from the community already stepped up to address this problem:
Without the help of the React Native community, especially Mike Grabowski and Lorenzo Sciandra, we would not be able to ship releases. We want to improve the release management process and plan to be more involved from now on:
* We will work with community members to create a blog post for each major release. * We will show breaking changes directly in the CLI when people upgrade to new versions. * We will reduce the time it takes to make a release. We are exploring ways to increase automated testing and also creating an improved manual test plan.
For the next two months, we will continue managing pull requests to stay on track while also starting to reduce the number of outstanding GitHub issues. We will continue reducing the surface area of React Native through the Lean Core project. We plan to address 5 of the top community problems. As we finalize the community guidelines, we will turn attention to our website and documentation.
We are very excited to host over ten contributors from our community at Facebook London in March to help drive several of these efforts. We are glad that you are using React Native and hope that youʼll see and feel the improvements we are working on in 2019. Weʼll be back with another update in a few months and will be merging your pull requests in the meantime! ⚛️✌️
HackerNewsBot debug: Calculated post rank: 106 - Loop: 96 - Rank min: 100 - Author rank: 338
VERSION 19.01 Has Been Released!
Took a bit longer than expected but I've found 31 new songs to add to the collection, bringing the total upto 442, with a combined playtime of almost 29 hours!
I also did a few minior changes, fixes and updates as usual.
You can check out and download the collection from here: https://juniorsdisk.com/
The next update should be out by the end of April assuming that everything goes well.
I'll add these songs to the bot soon.
Add finally, I would like to give a huge thank you to everyone who has been following, supporting and spreading the disk so far! =D
- The Compiler
#music #songs #diaspora #announcement #project #development #dev #mywork #update #community #thankyou #thanks
Yesterday a concerned Redis user wrote the following on Hacker News: — https://news.ycombinator.com/item?id=19204436 — I love Redis, but I'm a bit skeptical of some of the changes that are currently…
HN Discussion: https://news.ycombinator.com/item?id=19227070
Posted by mykowebhn (karma: 265)
Post stats: Points: 151 - Comments: 46 - 2019-02-22T17:21:41Z
#HackerNews #2019 #about #developments #redis #update
Yesterday a concerned Redis user wrote the following on Hacker News: — https://news.ycombinator.com/item?id=19204436 —
I love Redis, but Iʼm a bit skeptical of some of the changes that are currently in development. The respv3 protocol has some features that, while they sound neat, also could significantly complicate client library code. Thereʼs also a lot of work going into a granular acl. I canʼt imagine why this would be necessary, or a higher priority than other changes like multi-thread support, better persistence model, data-types, etc.
— end of user comment — I’ve the feeling she/he (not sure) is not the only one that looks at ACLs as some sort of feature imposed by the Redis Labs goals, because “enterprise users” or something like that. Also the other points in the comment are interesting, and I believe everything is very well worth addressing in order to communicate clearly with the Redis community what’s the road ahead. For simplicity I’ll split this blog post into sections addressing every single feature mentioned in the original comment. ## RESP3 The goal of RESP3, as I already blogged in these pages, is to actually simplify the clients landscape. Hopefully every client will have a lower layer that will not try to reinvent some kind of higher level interface: redis.call(“get”,”foo”). There is no longer need to orchestrate conversions because now the protocol is semantical enough to tell the client what a given reply should look like in the hand of the caller, nor any need to know beforehand the command fingerprint for the majority of commands. What I think the user is referring is RESP3 support for out of band communications, that is the reply “attributes”. I really believe that in the future of Redis “client side caching” will be a big thing. It’s the logical step in every scalable system. However without server assistance client side cache invalidation is a nightmare. This is the reason why RESP3 supports attributes in replies, mainly. However probably Redis 6 will not implement any of that. Redis unstable, that will become Redis 6, already has a RESP3 implementation that is almost complete, and there are no attributes. The clients implementing RESP3 can just decide to discard attributes if they are willing to be really future-proof, and likely attributes will not be sent at all anyway even for future Redis versions if the user did not activate some kind of special feature. For instance, for client side caching, the connection will have to be put in some special mode. Moreover, as you know, Redis 6 will be completely backward compatible with RESP2. Actually I’m starting to believe that RESP2 support will never be removed, because it is almost for free, and there is no good reason to break backward compatibility once we did the effort to implement the abstraction layer between RESP2 and RESP3. Normally I don’t like to change things without a good reason, however RESP2 limitations were having a strong effect on the client ecosystem. I would like to have a client landscape where users, going from one client to the other, will feel at home, and the API will be the Redis API, not the layer that the client author invented. I’m not against an higher level API in addition to the lower level one btw, but there should be a common ground, and clients should be able to send commands without knowing anything about such commands. ## ACLs The ACL specification was redacted by myself four years ago. I waited so much time in order to convince myself this was really the time to implement it: we went a long way without any ACL using just tricks, mainly command renaming. However don’t believe that ACLs main motivation is enterprise customers in need for security. As a side effect, ACLs also allow authentication of users for security purposes, but the main goal of the feature is operational. Let me show you an example. You have a Redis instance and you plan to use the instance to do a new thing: delayed jobs processing. You get a library from the internet, and it looks to work well. Now why on the earth such library, that you don’t know line by line, should be able to call “FLUSHALL” and flush away your database instantly? Maybe the library test will have such command inside and you realize it when it’s too late. Or maybe you just hired a junior developer that is keeping calling “KEYS ” on the Redis instance, while your company Redis policy is “No KEYS command”. Another scenario, cloud providers: they need to carefully rename the admin commands, and even to mask such commands from being leaked for some reason. More tricks: so MONITOR will not show the commands in the output for instance. With ACLs you can setup Redis so that default users, without some authentication, will be prevented to run anything that is administrative or dangerous. I think this will be a big improvement for operations. Moreover ACLs is one of the best code I wrote for Redis AFAIK. There is nearly no CPU cost at all, unless you se key patterns, but even so it’s small. The implementation is completely self contained inside the acl.c file, the rest of the core has a handful of calls to the ACL API. No complexity added to the system because it is completely modular. Actually the ACL code allowed to do some good refactoring around the AUTH command. ## Multi threading There are two possible multi threading supports that Redis could get. I believe the user is referring to “memcached alike” multithreading, that is the ability to scale a single Redis instance to multiple threads in order to increase the operations per second it can deliver in things like GET or SET and other simple commands. This involves making the I/O, command parsing and so forth multi threaded. So let’s call this thing “I/O threading”. Another multi threaded approach is to, instead, allow slow commands to be executed in a different thread, so that other clients are not blocked. We’ll call this threading model “Slow commands threading”. Well, that’s the plan: I/O threading is not going to happen in Redis AFAIK, because after much consideration I think it’s a lot of complexity without a good reason. Many Redis setups are network or memory bound actually. Additionally I really believe in a share-nothing setup, so the way I want to scale Redis is by improving the support for multiple Redis instances to be executed in the same host, especially via Redis Cluster. The things that will happen in 2019 about that are two: A) Redis Cluster multiple instances will be able to orchestrate to make a judicious use of the disk of the local instance, that is, let’s avoid an AOF rewrite at the same time. B) We are going to ship a Redis Cluster proxy as part of the Redis project, so that users are able to abstract away a cluster without having a good implementation of the Cluster protocol client side. Another thing to note is that Redis is not Memcached, but, like memcached, is an in-memory system. To make multithreaded an in-memory system like memcached, with a very simple data model, makes a lot of sense. A multi-threaded on-disk store is mandatory. A multi-threaded complex in-memory system is in the middle where things become ugly: Redis clients are not isolated, and data structures are complex. A thread doing LPUSH need to serve other threads doing LPOP. There is less to gain, and a lot of complexity to add. What instead I *really want a lot is slow operations threading, and with the Redis modules system we already are in the right direction. However in the future (not sure if in Redis 6 or 7) we’ll get key-level locking in the module system so that threads can completely acquire control of a key to process slow operations. Now modules can implement commands and can create a reply for the client in a completely separated way, but still to access the shared data set a global lock is needed: this will go away. ## Better persistence Recently we did multiple efforts in order to improve this kind of fundamental functions of Redis. One of the best thing that was implemented lately is the RDB preamble inside the AOF file. Also a lot of work went both in Redis 4 and 5 about replication, that is now completely at another level compared to what it used to be. And yes, it is still one of my main focus to improve such parts. ## Data structures Now Redis has Streams, starting with Redis 5. For Redis 6 and 7 what is planned is, to start, to make what we have much more memory efficient by changing the implementations of certain things. However to add new data structures there are a lot of considerations to do. It took me years to realize how to fill the gap, with streams, between lists, pub/sub and sorted sets, in the context of time series and streaming. I really want Redis to be a set of orthogonal data structures that the user can put together, and not a set of tools that are ready to use. Streams are an abstract log, so I think it’s a very worthwhile addition. However other things I’m not completely sure if they are worth to be inside the core without a very long consideration. Anyway in the latest years there was definitely more stress in adding new data structures. HyperLogLogs, more advanced bit operations, streams, blocking sorted set operations (ZPOP* and BZPOP*), and streams are good examples. ## Conclusions I believe that the Redis community should be aware about why something is done and why something is instead postponed. I do the error to communicate a lot via Twitter like if everybody is there, but many people happen to have a life 😁 and don’t care. The blog is a much better way to inform the community, I need to take the time to blog more. Incidentally I love to write posts, so it’s a win-win. An important thing to realize is that Redis has not a solid roadmap, over the years I found that opportunistic development is a huge win over having a roadmap. Something is demanded? I see the need? I’m in the mood to code it? It’s the right moment because there are no other huge priorities? There are a set of users that are helping the design process, giving hints, ideas, testing stuff? It’s the right moment, let’s do it. To have a solid roadmap for Redis is silly because the size of the OSS core team is small, sometimes I remain stuck with some random crash for weeks… Any fixed long term plan would not work. Moreover as the Redis community gives feedbacks my ideas change a lot, so I would rewrite the roadmap every month. Yet blogging is a good solution to at least show what is the current version of the priorities / ideas, and to show why other ideas were abandoned. A final note: the level of freedom Iʼve with Redis Labs about what to put inside the open source project side is almost infinite. I think this is kinda of a miracle in the industry, or just the people I work with at Redis Labs are nice folks that understand that what we are doing originated from the open source movement and is wise to keep it going in that way. But itʼs not a common thing. If I do errors in the Redis roadmap they are surely my errors.
HackerNewsBot debug: Calculated post rank: 116 - Loop: 159 - Rank min: 100 - Author rank: 55
Edit: sorry posted the first time the wrong URL.
This is another minor bugfix update from us, which we recommend you install.
Download Deluge firmware V2.1.2
* Fixed - samples in CUT or STRETCH mode could cut out while recording from song view to arranger
* Fixed bug when a folder contained both files with note numbers in their names, and files without
* Fixed rare misbehaviour relating to editing or recording into the arranger
* Fixed potential crash if you press the keyboard button while in a menu
* Fixed bug where song’s stored tempo could end up slightly off after playing with Deluge slaved to another device
* Fixed minor visual glitch in arranger view when playing many samples
* Fixed problem which could result in vertical scroll ending up far out of range
* Fixed bug where wrong kit sounds could be triggered via audition pads if a different track was currently being played back on that same kit
* Beginning playback mid-way through a long arpeggiated note now lets it sound
To install the update, place the .bin file onto your SD card, ensure there are no other .bin files on there, put the card back into your Deluge, and then hold down the shift button while powering on. A spinning animation will display, and the firmware will be permanently installed.
We recommend you take the opportunity to back up the contents of your SD card while it's in your computer.
#Deluge #Synthstrom #Firmware #Update #Newsletter
#ZDF #heute-show #ZDFheuteshow #NicoSemsrott #KünstlicheIntelligenz #KI #Captcha #Smartphone #Lüngenpresse #Diesel #Feinstaub #Lungenarzt #DieterKöhler #Update #Maschine #Ampel #Spielen #Auto #Pixel #Supermarkt #Pfandflaschen #Leergutautomat #Experte #Autobahn #Eco-Tipp #Volkswagen
#Linux Testwoche Tag 4 - Wie, man muss nicht #Neustarten?
Keine Woche #Linux und mir fällt jetzt schon eine Sache auf: Wie selten muss man denn den Rechner neu starten? Ich habe gefühlt schon 20 #Programme installiert und wieder deinstalliert und täglich bekommen einige #Pakete Updates doch stets im #Hintergrund, stets nicht aufdringlich und mit einer grandiosen #Geschwindigkeit. Hier mal beispielhaft am #Browser #Vivaldi in der #Windows-Version erklärt, was ich meine:
Beim Starten kommt die Information, das ein #Update verfügbar ist. Wenn man bestätigt wird es heruntergeladen, dabei ploppt das kleine Fenster beim Anfang, bei 99% und nochmal Wenn fertig in den Vordergrund und man kann es nicht minimieren. Wenn man es installiert muss der #Browser im Hintergrund geschlossen werden oder ein Neustart steht an. Schließt man dann den #Browser steht zu 99% dennoch ein #Neustart an. Hinterher startet man #Vivaldi und der Startvorgang muss erst mal alle #Addons (bei mir ganze eins) für die neue #Version optimieren. Der ganze Vorgang dauert mich gefühlt 45 Minuten. Das alles für einen #Browser ehrlich? Wenn das jetzt alle halben Jahre mal passieren würde, doch auch kleinste Versionssprünge, teilweise über Wochen werden derart hart zelebriert. #LinuxMint: Oh #Update. Oh installiert. Oh beim nächsten Browserstart sofort fertig. Geil.
Zentrale Paketverwaltung - Bei #Thors Hammer ist das geil
Im Hintergrund läuft stets eine Anwendung die sich um #Aktualisierungen kümmert. Nicht nur fürs #System, nein für beinahe ALLE Pakete. Bei #Windows war ich es ja schon fast gewohnt, das man von den 20 benutzen #Programmen täglich eines immer ein Update haben will und man dann viel Zeit verliert beim herunterladen, installieren und oft #Neustarten. Die letzten Tage bei #Mint wurde ich erst einmal beim installieren des #Graka Treibers zum Neustarten aufgefordert und seitdem nicht wieder.
Ich hatte mit viel mehr Problemen gerechnet.
Jetzt da ich schon ein paar Tage #Mint verwende muss ich als erstes #Fazit ziehen: Das mit Abstand schwierigste war es den verfickten #Boot-Stick unter Windows zu erstellen und eine passende #Distribution zu finden. Alles andere was ich brauche ist entweder selbsterklärend, oder finde ich auf #ubuntuusers.de. #Gaming, #Streaming, #Videoschnitt folgt dann dieses Wochenende. Genauer gesagt morgen ab 20 Uhr auf twitch.tv/bubborch wird gestreamt. Irgendein Spiel, welches eigentlich für #Windows gedacht ist, ich schätze #Batman
#EineSorgeWeniger on Twitter #EineSorgeWeniger”
Ab 8. April wird es wohl viele Sonderangebote geben...
Ich habe noch ein saualtes TomTom GO 500, was eigentlich ganz gut funktioniert. Gut, der Akku ist hinüber. Die Karten sind out of date.
Die Kartenabweichungen jucken mich nicht wirklich. Und angesteckt ist es eh immer.
Aber jetzt ist wohl Schluß mit dem Ding. Dann wird es wohl nur noch eine Freisprecheinrichtung...
Da gibt es bestimmt einige, die das nutzen, um Reibach zumachen...
#GPS #Update #navi
Your GPS Devices May Stop Working On April 6 If You Don't Or Can't Update Firmware - Slashdot
Zorro shares a report from The Register: Older satnavs and such devices won't be able to use America's Global Positioning System properly after April 6 unless they've been suitably updated or designed to handle a looming epoch rollover. GPS signals from satellites include a timestamp, needed in par...